windbg command line option for Disable dialog box

Hi,
can any one please help… i need a command line option to disable the dialog box for windbg… i used -QY, but i ned an option that disables all kind of dialog box, not only the save workspace…

I need to disable the dialog box that appears when i provide an incomaptible dump file…
i uploaded jpeg and got the following -

Loading Dump File [C:\javaw_threads.jpg]
Could not match Dump File signature - invalid file format
Could not open dump file [C:\javaw_threads.jpg], Win32 error 0n87
“The parameter is incorrect.”

how to disable above dailog box…
Your help is much appreciated!!!

You can use KD instead of WinDBG. What exactly are you trying to do?

Kris

Or write a simple DbgEng based utility to open the dump file and run some
commands. See the dumpstk sample in the SDK.

-scott


Scott Noone
Consulting Associate and Chief System Problem Analyst
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Krzysztof Uchronski” wrote in message news:xxxxx@windbg…

You can use KD instead of WinDBG. What exactly are you trying to do?

Kris

i dont want to use KD… i will be accessing the user dumps as well… i am automating windbg session… but if an incomaptible file is recieved windbg shows a dialog box with win32 error 0n87

xxxxx@yahoo.com wrote:

Hi,
can any one please help… i need a command line option to disable the dialog box for windbg… i used -QY, but i ned an option that disables all kind of dialog box, not only the save workspace…

I need to disable the dialog box that appears when i provide an incomaptible dump file…
i uploaded jpeg and got the following -

Loading Dump File [C:\javaw_threads.jpg]
Could not match Dump File signature - invalid file format
Could not open dump file [C:\javaw_threads.jpg], Win32 error 0n87
“The parameter is incorrect.”

how to disable above dailog box…
Your help is much appreciated!!!

This is a very odd request. If you want to check whether a dump is
valid, use the “dumpchk.exe” command. If you want a command-line dump
analyzer tool, you should use “kd.exe” or “dumpexam,exe”.

Of course, the best advice is “don’t don’t pass JPEG images to windbg”.

i dont want to use KD…

I think that’s only because you haven’t thought about what you’re
doing. WinDbg is just a GUI wrapper around kd.exe.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

thanks for your reply tim,
ofcourse no one would be passing the jpeg to windbg, i was just stress testing it, because i just found that windbg just processes few of the files even if they are not crash dump and returns unknown bugchechk.
anyways…my question was around the option of disabling all the dialog boxes in a similar way as we have for save workspace dialog box -QY option.

second—
I meant i dont want to use KD because i would need both KD and CDB…

USE AT OWN RISK MAY HAVE SIDE EFFECTS

if you are stubborn about it and can employ come what may approach to
your own windbg installation

patch windbg!Infobox with a ret

016FFD5C 0102ACA6 RETURN to windbg.0102ACA6 from windbg.InfoBox
016FFD60 00000408
016FFD64 008096C8 UNICODE “C:\Documents and
Settings\Admin\Desktop\pp_002.jpeg”
016FFD68 01079FC0 UNICODE “Win32 error 0n87”
016FFD6C 01079738 UNICODE “The parameter is incorrect.”

this can eliminate the msgbox from all these function

Call tree
Called from Procedure
Calls directly
Comment
windbg.WinCommandTree::CreateAndLoad+4E
windbg.InfoBox
windbg.FormatMsgBoxV
windbg.WinCommandTree::CreateAndLoad+7B
windbg.01015CB1
windbg.WinBase::DoWriteTextToFile+81
windbg.WinBase::DoWriteTextToFile+0EB
windbg.WinBase::ChangeAllDock+5F
windbg.WinBase::TileFloatingWindows+17C
windbg.WinBase::FinalizeAllAppliedWorkspaces+1B3
windbg.0101DC15
windbg.01021090
windbg.01022E7D
windbg.ProcessCommand+24C
windbg.ConvertAttachToCreate+7C
windbg.ConvertAttachToCreate+0C8
windbg.010297D6
windbg.0102984D
windbg.0102987D
windbg.010298DB
windbg.01029950
windbg.InitializeEngineInterfaces+4D
windbg.InitializeEngineInterfaces+17C
windbg.InitializeEngineInterfaces+1AA
windbg.InitializeEngineInterfaces+2A5
windbg.InitializeEngineInterfaces+409
windbg.InitializeEngineInterfaces+473
windbg.InitializeEngineInterfaces+4E6
windbg.InitializeEngineInterfaces+586
windbg.InitializeEngineInterfaces+649
windbg.InitializeEngineInterfaces+6F8
windbg.InitializeEngineInterfaces+772
windbg.InitializeEngineInterfaces+7CA
windbg.InitializeEngineInterfaces+818
windbg.InitializeEngineInterfaces+871
windbg.StartSession+0EC
windbg.0102ACA1
windbg.0102ACD5
windbg.0102AE08
windbg.0102AE8E
windbg.0102AEBE
windbg.0102AF91
windbg.0102AFC1
windbg.0102B02F
windbg.0102B126
windbg.0102B14F
windbg.0102B183
windbg.0102B8C4
windbg.01035AE5
windbg.InitUiBufferInfo+62
windbg.01035DEC
windbg.010374B2
windbg.FillSourcePathText+73
windbg.01037817
windbg.010378D2
windbg.AcceptDropFiles+9A
windbg.0103EE8E
windbg.0103F805
windbg.0103F8CB
windbg.RichEditFind+17E
windbg.0104B50D
windbg.CreateUiInterfaces+43
windbg.CreateUiInterfaces+5B
windbg.CreateUiInterfaces+8F
windbg.CreateUiInterfaces+0BC
windbg.CreateUiInterfaces+125
windbg.CreateUiInterfaces+168
windbg.CreateUiInterfaces+196
windbg.CreateUiInterfaces+1F4
windbg.CreateUiInterfaces+221
windbg.CreateUiInterfaces+24F
windbg.CreateUiInterfaces+291
windbg.CreateUiInterfaces+2BF
windbg.CreateUiInterfaces+301
windbg.CreateUiInterfaces+32F
windbg.CreateUiInterfaces+371
windbg.CreateUiInterfaces+39F
windbg.CreateUiInterfaces+467
windbg.ParseCommandLine+577
windbg.ParseCommandLine+58C
windbg.ParseCommandLine+5EC
windbg.ParseCommandLine+601
windbg.ParseCommandLine+64C
windbg.ParseCommandLine+661
windbg.01053B92
windbg.01053EB0
windbg.01054214
windbg.01054297
windbg.0105430E
windbg.01054460
windbg.010544EC
windbg.0105459C
windbg.01054817
windbg.wmain+183
windbg.wmain+1C1
windbg.wmain+205
windbg.UiSwitchToExplicitWorkspace+38
windbg.UiSwitchToExplicitWorkspace+61
windbg.UiSaveWorkspaceAs+86
windbg.EngSwitchWorkspace+17D

or run windbg on windbg and use conditional breakpoint to patch windbg
on the fly :slight_smile:

0:003> bl
0 e 0104f350 0001 (0001) 0:**** windbg!InfoBox “eb eip 0xc3;du
poi(esp+8);.echo "testbp_for_sarika_wadhwa";g”
0:003> g
00b71f60 "C:\Documents and Settings\Admin"
00b71fa0 “Desktop\pp_002.jpeg”
testbp_for_sarika_wadhwa
00b71f60 "C:\Documents and Settings\Admin"
00b71fa0 “Desktop\pf.xls”
testbp_for_sarika_wadhwa
00b71f60 "C:\Documents and Settings\Admin"
00b71fa0 “Desktop\Thumbs.db”
testbp_for_sarika_wadhwa
00b71f60 "C:\Documents and Settings\Admin"
00b71fa0 “Desktop\shl1.tmp.txt.CSV”
testbp_for_sarika_wadhwa

regards
raj

On 7/21/11, xxxxx@yahoo.com wrote:
> thanks for your reply tim,
> ofcourse no one would be passing the jpeg to windbg, i was just stress
> testing it, because i just found that windbg just processes few of the files
> even if they are not crash dump and returns unknown bugchechk.
> anyways…my question was around the option of disabling all the dialog boxes
> in a similar way as we have for save workspace dialog box -QY option.
>
> second—
> I meant i dont want to use KD because i would need both KD and CDB…
>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>


thanks and regards

raj_r