There are some old posts in the archive of this mailing list explaining in
some detail why the breakpoints won’t get instantiated unless the target
is stopped. I’ll summarize by saying that it’s “by design”.
Phil
Philip D. Barila
Seagate Technology LLC
(720) 684-1842
“M Harvey”
Sent by: xxxxx@lists.osr.com
No Phone Info Available
12/06/2004 04:20 AM
Please respond to
“Kernel Debugging Interest List”
To
“Kernel Debugging Interest List”
cc
Subject
Re:[windbg] (windbg) Catching breakpoints during Windows startup
Hi,
I’ve not used 1394 for debugging (I normally use serial), but it seems to
me
that the debug isn’t getting a chance to insert the breakpoint after the
boot.
Try stopping the target just after the debugger detects that it has
booted, then
type “.reload” at the prompt, and “g” to continue the target.
WinDbg ocasionally won’t or can’t set breakpoints - but it’s almost always
because the debugger hasn’t had a time to insert the breakpoint, or
because the
symbols are bad.
MH.
Reply Separator
Subject: (windbg) Catching breakpoints during Windows startup
Author: “Takin Nili-Esfahani” smtp:xxxxx
Date: 04/12/2004 06:48
Hi,
If I set a breakpoint on DriverEntry and load the driver interactively,
for
example by installing the .inf file, WinDbg catches the breakpoint as
expected. However, if I restart the machine, the same breakpoint will not
get hit during Windows startup. I know that Windows is loading the driver
since I can see trace statements coming from DriverEntry.
I am using 1394 and WinDbg is re-attaching to the target correctly after
it
is rebooted.
I think if I hard code a breakpoint in DriverEntry, it should break into
the
debugger but I would rather save that as a last resort.
Does anyone know why this is happening?
Takin
—
You are currently subscribed to windbg as: xxxxx@snellwilcox.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
This email and any attachments is confidential, may be legally privileged
and is intended for the use of the addressee only. If you are not the
intended recipient, please note that any use, disclosure, printing or
copying of this email is strictly prohibited and may be unlawful. If
received in error, please delete this email and any attachments and
confirm this to the sender.
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com</smtp:xxxxx>