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

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

Scripting WinDBG to process captured minidumps

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_NooneScott_Noone Posts: 2,989
    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
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!