windbg - won't tigger breakpoint until after manual break (load symbols)
in [Device Drivers]
|
Prev: help - added IRP_MJ_READ to toaster sample....bluescreen.
Next: windbg - won't tigger breakpoint until after manual break
From: David F. on 8 Jun 2010 13:18 Hi, I don't recall this being a problem in the past, but if I set a break point on something like DriverEntry, it's never hit, unless I manually break as soon as windbg attaches, then go. It's like the symbols aren't loaded until that point? I also don't see the driver in the list of stuff it's loading symbols for when doing the manual break (I thought it used to in the past? - also !reload or .reload also doesn't). Maybe I messed up some setting somewhere? Do any of the WinDbg experts have an idea what's up?? TIA!!
From: Maxim S. Shatskih on 8 Jun 2010 13:31 You can also use "Break on module load" feature. -- Maxim S. Shatskih Windows DDK MVP maxim(a)storagecraft.com http://www.storagecraft.com "David F." <df2705(a)community.nospam> wrote in message news:7D000D8A-8276-4C42-96E3-BA02B069FCF2(a)microsoft.com... > Hi, > > I don't recall this being a problem in the past, but if I set a break point > on something like DriverEntry, it's never hit, unless I manually break as > soon as windbg attaches, then go. It's like the symbols aren't loaded > until that point? I also don't see the driver in the list of stuff it's > loading symbols for when doing the manual break (I thought it used to in the > past? - also !reload or .reload also doesn't). Maybe I messed up some > setting somewhere? Do any of the WinDbg experts have an idea what's up?? > > TIA!! >
From: David F. on 8 Jun 2010 18:57
glad to see I'm in good company. Thanks for the tips. |