Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


Scripting WinDBG to process captured minidumps

Osiris_PedrosoOsiris_Pedroso Member Posts: 24
I script windbg.exe to process minidumps captured in my QA organization,
which can amount to thousands every couple of weeks.

This is the PowerShell script I use to run my script after preparing the
input files:
============= run-triage-windbg.ps1 ==================
[CmdletBinding()]
Param ()
Set-StrictMode -version latest # inform of uninitialized variables
$ErrorActionPreference = 'Stop'
$VerbosePreference = 'Continue'

$windbgexe = 'c:\Program Files (x86)\Windows
Kits\10\Debuggers\x64\windbg.exe'
$windbgargs = @('-WX','-QSY',"-logo `"${Env:WINDBG_LOG}`"","-c
`"`$`<${Env:TRIAGE_WINDBGCMDS_FILE}`"","-y `"${Env:_NT_SYMBOL_PATH}`"","-z
${Env:dmpFile}")

$proc = Start-Process $windbgexe -Passthru -WindowStyle Hidden
-ArgumentList $windbgargs
($proc).PriorityClass='BelowNormal'
Wait-Process -InputObject $proc
$proc.ExitCode
====================================================

My problem is that even though the WinDBG main GUI window is not shown
(due to -WindowStyle Hidden), the window titled "Command - Dump ..... -
WinDbg: 10.0.10586.567 AMD64" still gets displayed while the script is
running.

Is there any way to make sure that window gets created docked by default? I
currently run without any workspaces.

Appreciate your input,
Osiris Pedroso

Comments

  • Scott_Noone_(OSR)Scott_Noone_(OSR) Administrator Posts: 3,302
    I'm not sure I completely understand the problem, but maybe try using the
    command line version (kd.exe) instead? It should take the same command line
    arguments as WinDbg.

    -scott
    OSR
    @OSRDrivers

    -scott
    OSR

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Kernel Debugging 30 Mar 2020 OSR Seminar Space
Developing Minifilters 15 Jun 2020 LIVE ONLINE
Writing WDF Drivers 22 June 2020 LIVE ONLINE
Internals & Software Drivers 28 Sept 2020 Dulles, VA