Driver Problems? Questions? Issues?
Put OSR's experience to work for you! Contact us for assistance with:
  • Creating the right design for your requirements
  • Reviewing your existing driver code
  • Analyzing driver reliability/performance issues
  • Custom training mixed with consulting and focused directly on your specific areas of interest/concern.
Check us out. OSR, the Windows driver experts.

Go Back   OSR Online Lists > windbg
Welcome, Guest
You must login to post to this list
  Message 1 of 2  
02 Oct 17 15:46
Osiris Pedroso
Join Date: 21 May 2010
Posts To This List: 24
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 --
  Message 2 of 2  
03 Oct 17 09:12
Scott Noone
Join Date: 10 Jul 2002
Posts To This List: 558
List Moderator
Scripting WinDBG to process captured minidumps

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
Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You must login to OSR Online AND be a member of the windbg list to be able to post.

All times are GMT -5. The time now is 17:06.

Copyright ©2015, OSR Open Systems Resources, Inc.
Based on vBulletin Copyright ©2000 - 2005, Jelsoft Enterprises Ltd.
Modified under license