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 just need one more step, and that is to set the Initial Breakpoint.
Once the system has broken, the saved breakpoints are instantiated and
will work as expected.
Phil
Philip D. Barila
Seagate Technology LLC
(720) 684-1842
“Takin Nili-Esfahani”
Sent by: xxxxx@lists.osr.com
No Phone Info Available
12/03/2004 11:48 PM
Please respond to
“Kernel Debugging Interest List”
To
“Kernel Debugging Interest List”
cc
Subject
[windbg] Catching breakpoints during Windows startup
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@seagate.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
One simple way to handle this is to use the /break on the boot.ini line for
the debugger. This forces an initial break early in the system load time.
Just be aware that if you do not have the debugger connected the system will
fault on the breakpoint, as it will with any hard coded breakpoints.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
wrote in message news:xxxxx@windbg…
You just need one more step, and that is to set the Initial Breakpoint.
Once the system has broken, the saved breakpoints are instantiated and will
work as expected.
Phil
Philip D. Barila
Seagate Technology LLC
(720) 684-1842
“Takin Nili-Esfahani”
Sent by: xxxxx@lists.osr.com
No Phone Info Available
12/03/2004 11:48 PM Please respond to
“Kernel Debugging Interest List”
To"Kernel Debugging Interest List"
cc
Subject[windbg] Catching breakpoints during Windows startup
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@seagate.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
I found going to Debug | Kernel Connection | Cycle Initial Break to satisfy
my needs. Thanks for this extra bit of info though.
I am curious why this extra step is necessary though.
Takin
“Don Burn” wrote in message news:xxxxx@windbg…
> One simple way to handle this is to use the /break on the boot.ini line
for
> the debugger. This forces an initial break early in the system load time.
> Just be aware that if you do not have the debugger connected the system
will
> fault on the breakpoint, as it will with any hard coded breakpoints.
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
> wrote in message news:xxxxx@windbg…
>
> You just need one more step, and that is to set the Initial Breakpoint.
> Once the system has broken, the saved breakpoints are instantiated and
will
> work as expected.
>
> Phil
>
> Philip D. Barila
> Seagate Technology LLC
> (720) 684-1842
>
>
> “Takin Nili-Esfahani”
> Sent by: xxxxx@lists.osr.com
> No Phone Info Available
> 12/03/2004 11:48 PM Please respond to
> “Kernel Debugging Interest List”
>
> To"Kernel Debugging Interest List"
> cc
> Subject[windbg] Catching breakpoints during Windows startup
>
>
>
>
>
>
>
> 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@seagate.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>