windbg - won't tigger breakpoint until after manual break
in [Device Drivers]
|
Prev: windbg - won't tigger breakpoint until after manual break (load symbols)
Next: Post Script Print Driver - Need Help
From: Don Burn on 8 Jun 2010 13:24 Depends on a lot of things, but I see this pretty often. Either use /break (assuming boot.ini) or put a hard coded breakpoint in the beginning of your DriverEntry. Otherwise, I never know for sure whether windbg will break. Don Burn (MVP, Windows DKD) Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr > -----Original Message----- > From: David F. [mailto:df2705(a)community.nospam] > Posted At: Tuesday, June 08, 2010 1:19 PM > Posted To: microsoft.public.development.device.drivers > Conversation: windbg - won't tigger breakpoint until after manual break (load > symbols) > Subject: 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!! > > > __________ Information from ESET Smart Security, version of virus signature > database 5182 (20100608) __________ > > The message was checked by ESET Smart Security. > > http://www.eset.com > |