Windbg in DriverEntry Routine

NTDEV
1

I am trying to debug my driver’s DriverEntry routine, but windbg ignores
all breakpoints set until the driver is running, and it can load the
symbols, and then i can set breakpoints. Is there a way to get WinDbg to
break on DriverEntry?
I have the symbols path set to d:\debug, and the executables path was
either the network share to the debug computers -
\winntdebug\c\winnt\system32\drivers, and i also copied the .sys to
d:\debug, and set the executable path to d:\debug, and nothing has
worked so far.
Any help would be appreciated.
Thanx
Nachum

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

Ctrl+Alt+K to cycle the Initial Breakpoint. When you hit the breakpoint on
connect, set your breakpoints, then go.
-----Original Message-----
From: Nachum Kanovsky [mailto:xxxxx@yahoo.com]
Sent: Thursday, July 19, 2001 10:36 AM
To: NT Developers Interest List
Subject: [ntdev] Windbg in DriverEntry Routine

I am trying to debug my driver’s DriverEntry routine, but windbg ignores all
breakpoints set until the driver is running, and it can load the symbols,
and then i can set breakpoints. Is there a way to get WinDbg to break on
DriverEntry?
I have the symbols path set to d:\debug, and the executables path was either
the network share to the debug computers -
\winntdebug\c\winnt\system32\drivers
<file:> , and i also copied the .sys
to d:\debug, and set the executable path to d:\debug, and nothing has worked
so far.
Any help would be appreciated.
Thanx
Nachum
—
You are currently subscribed to ntdev as: xxxxx@intel.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com</file:>

3

I’m assuming here that you are using the latest beta, 3.00.0010. Use
CTL+ALT+K to set an system initialization breakpoint. Once there you can use
“bu MyDriver!DriverEntry”.

Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@broadstor.com

-----Original Message-----
From: Nachum Kanovsky [mailto:xxxxx@yahoo.com]
Sent: Thursday, July 19, 2001 10:36 AM
To: NT Developers Interest List
Subject: [ntdev] Windbg in DriverEntry Routine

I am trying to debug my driver’s DriverEntry routine, but windbg ignores all
breakpoints set until the driver is running, and it can load the symbols,
and then i can set breakpoints. Is there a way to get WinDbg to break on
DriverEntry?
I have the symbols path set to d:\debug, and the executables path was either
the network share to the debug computers -
\winntdebug\c\winnt\system32\drivers
<file:> , and i also copied the .sys
to d:\debug, and set the executable path to d:\debug, and nothing has worked
so far.
Any help would be appreciated.
Thanx
Nachum
—
You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com</file:>

4

Hello,
Use Ctrl+Alt+k in Windbg to set an initial breakpoint, then reboot
target machine. This will break in on first symbol load at next boot of
the target. When breaks, you can set breakpoints at the driver’s
DriverEntry routine and then hit go.
Khalid

-----Original Message-----
From: Nachum Kanovsky [mailto:xxxxx@yahoo.com]
Sent: Thursday, July 19, 2001 10:36 AM
To: NT Developers Interest List
Subject: [ntdev] Windbg in DriverEntry Routine

I am trying to debug my driver’s DriverEntry routine, but windbg ignores
all breakpoints set until the driver is running, and it can load the
symbols, and then i can set breakpoints. Is there a way to get WinDbg to
break on DriverEntry?
I have the symbols path set to d:\debug, and the executables path was
either the network share to the debug computers -
\winntdebug\c\winnt\system32\drivers
<file:> , and i also copied the
.sys to d:\debug, and set the executable path to d:\debug, and nothing
has worked so far.
Any help would be appreciated.
Thanx
Nachum
—
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com</file:>

5

Khalid,my problem is similer to this.(windbg
3.0.0010.0)

I am able to set breakpoint(red color) in DriverEntry.

Restart the target to go into the DriverEntry.

Target system is loaded completly but nither any
breakpoint hit of DriverEntry .

waiting for suggetion.

John

— Khalid Sabri wrote: >
Hello,
> Use Ctrl+Alt+k in Windbg to set an initial
> breakpoint, then reboot
> target machine. This will break in on first symbol
> load at next boot of
> the target. When breaks, you can set breakpoints at
> the driver’s
> DriverEntry routine and then hit go.
> Khalid
>
> -----Original Message-----
> From: Nachum Kanovsky [mailto:xxxxx@yahoo.com]
> Sent: Thursday, July 19, 2001 10:36 AM
> To: NT Developers Interest List
> Subject: [ntdev] Windbg in DriverEntry Routine
>
> I am trying to debug my driver’s DriverEntry
> routine, but windbg ignores
> all breakpoints set until the driver is running, and
> it can load the
> symbols, and then i can set breakpoints. Is there a
> way to get WinDbg to
> break on DriverEntry?
> I have the symbols path set to d:\debug, and the
> executables path was
> either the network share to the debug computers -
> \winntdebug\c\winnt\system32\drivers
> <file:> ,
> and i also copied the
> .sys to d:\debug, and set the executable path to
> d:\debug, and nothing
> has worked so far.
> Any help would be appreciated.
> Thanx
> Nachum
> —
> You are currently subscribed to ntdev as:
> xxxxx@microsoft.com
> To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.co.uk
> To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>

____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com</file:>

6

Like Khalid said, you need to hit the “initial breakpoint” before *your*
breakpoints will be instantiated. That is a design decision that the MS
debugger team made some time back and has been discussed at length here
several times. Just do what Khalid said, exactly as he said it, and you
should have no problem getting your breakpoints.

-----Original Message-----
From: malcom john [mailto:xxxxx@yahoo.co.uk]
Sent: Thursday, July 19, 2001 11:34 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Windbg in DriverEntry Routine

Khalid,my problem is similer to this.(windbg
3.0.0010.0)

I am able to set breakpoint(red color) in DriverEntry.

Restart the target to go into the DriverEntry.

Target system is loaded completly but nither any
breakpoint hit of DriverEntry .

waiting for suggetion.

John

— Khalid Sabri wrote: >
Hello,
> Use Ctrl+Alt+k in Windbg to set an initial
> breakpoint, then reboot
> target machine. This will break in on first symbol
> load at next boot of
> the target. When breaks, you can set breakpoints at
> the driver’s
> DriverEntry routine and then hit go.
> Khalid
>
> -----Original Message-----
> From: Nachum Kanovsky [mailto:xxxxx@yahoo.com]
> Sent: Thursday, July 19, 2001 10:36 AM
> To: NT Developers Interest List
> Subject: [ntdev] Windbg in DriverEntry Routine
>
> I am trying to debug my driver’s DriverEntry
> routine, but windbg ignores
> all breakpoints set until the driver is running, and
> it can load the
> symbols, and then i can set breakpoints. Is there a
> way to get WinDbg to
> break on DriverEntry?
> I have the symbols path set to d:\debug, and the
> executables path was
> either the network share to the debug computers -
> \winntdebug\c\winnt\system32\drivers
> <file:> ,
> and i also copied the
> .sys to d:\debug, and set the executable path to
> d:\debug, and nothing
> has worked so far.
> Any help would be appreciated.
> Thanx
> Nachum
> —
> You are currently subscribed to ntdev as:
> xxxxx@microsoft.com
> To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.co.uk
> To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>

____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie

—
You are currently subscribed to ntdev as: xxxxx@intel.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com</file:>

7

Yeah, it should work
Khalid

-----Original Message-----
From: Barila, Phil [mailto:xxxxx@intel.com]
Sent: Friday, July 20, 2001 8:24 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Windbg in DriverEntry Routine

Like Khalid said, you need to hit the “initial breakpoint” before *your*
breakpoints will be instantiated. That is a design decision that the MS
debugger team made some time back and has been discussed at length here
several times. Just do what Khalid said, exactly as he said it, and you
should have no problem getting your breakpoints.

-----Original Message-----
From: malcom john [mailto:xxxxx@yahoo.co.uk]
Sent: Thursday, July 19, 2001 11:34 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Windbg in DriverEntry Routine

Khalid,my problem is similer to this.(windbg
3.0.0010.0)

I am able to set breakpoint(red color) in DriverEntry.

Restart the target to go into the DriverEntry.

Target system is loaded completly but nither any
breakpoint hit of DriverEntry .

waiting for suggetion.

John

— Khalid Sabri wrote: >
Hello,
> Use Ctrl+Alt+k in Windbg to set an initial
> breakpoint, then reboot
> target machine. This will break in on first symbol
> load at next boot of
> the target. When breaks, you can set breakpoints at
> the driver’s
> DriverEntry routine and then hit go.
> Khalid
>
> -----Original Message-----
> From: Nachum Kanovsky [mailto:xxxxx@yahoo.com]
> Sent: Thursday, July 19, 2001 10:36 AM
> To: NT Developers Interest List
> Subject: [ntdev] Windbg in DriverEntry Routine
>
> I am trying to debug my driver’s DriverEntry
> routine, but windbg ignores
> all breakpoints set until the driver is running, and
> it can load the
> symbols, and then i can set breakpoints. Is there a
> way to get WinDbg to
> break on DriverEntry?
> I have the symbols path set to d:\debug, and the
> executables path was
> either the network share to the debug computers -
> \winntdebug\c\winnt\system32\drivers
> <file:> ,
> and i also copied the
> .sys to d:\debug, and set the executable path to
> d:\debug, and nothing
> has worked so far.
> Any help would be appreciated.
> Thanx
> Nachum
> —
> You are currently subscribed to ntdev as:
> xxxxx@microsoft.com
> To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.co.uk
> To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>

____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie

—
You are currently subscribed to ntdev as: xxxxx@intel.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com</file:>

8

I found that the major problem i was having is that i have a cpl with
the same name, being mango, ie: mango.cpl, and mango.sys, and that
before mango.sys was loaded, it kept assuming that i was referring to a
function in the cpl file, once i renamed the file, then using the
deferred breakpoint worked fine, thanx.
nachum
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Khalid Sabri
Sent: Friday, July 20, 2001 2:39 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Windbg in DriverEntry Routine

Hello,
Use Ctrl+Alt+k in Windbg to set an initial breakpoint, then reboot
target machine. This will break in on first symbol load at next boot of
the target. When breaks, you can set breakpoints at the driver?s
DriverEntry routine and then hit go.
Khalid

-----Original Message-----
From: Nachum Kanovsky [mailto:xxxxx@yahoo.com]
Sent: Thursday, July 19, 2001 10:36 AM
To: NT Developers Interest List
Subject: [ntdev] Windbg in DriverEntry Routine

I am trying to debug my driver’s DriverEntry routine, but windbg ignores
all breakpoints set until the driver is running, and it can load the
symbols, and then i can set breakpoints. Is there a way to get WinDbg to
break on DriverEntry?
I have the symbols path set to d:\debug, and the executables path was
either the network share to the debug computers -
\winntdebug\c\winnt\system32\drivers
<file:> , and i also copied the
.sys to d:\debug, and set the executable path to d:\debug, and nothing
has worked so far.
Any help would be appreciated.
Thanx
Nachum
—
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: xxxxx@yahoo.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com</file:>