windbg - won't tigger breakpoint until after manual break (load symbols)

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!!

You can also use "Break on module load" feature.

--
Maxim S. Shatskih
Windows DDK MVP

http://www.storagecraft.com

"David F." <> wrote in message news:7D000D8A-8276-4C42-96E3-...
> 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!!
>

glad to see I'm in good company. Thanks for the tips.