using windbg - newbie

I’m trying to debug for the first time. I compiled and installed the mirror
driver sample and now I want to see what’s going on behind the scenes.
Since this is my first device driver, I’d like to set breakpoints all over
the code and watch what’s going on so I can learn.

What isn’t clear to me is how windbg works. Do I run it on the machine that
has the source code? I do have two machines, with a null modem and both are
at COM1. They can talk to each other through hyperterminal without a
problem, so the hardware link is established.

Now, I have the source code on my laptop and I also have a line in the
boot.ini like this:
multi(0)disk(0)rdisk(0)partition(2)\WINNT=“Microsoft Windows 2000 Server
(Debug)” /fastdetect /sos /debug /debugport=COM1 /baudrate=115200

Then I run windbg on my desktop and boot the laptop using the boot entry
above. It starts to load drivers and then hangs.

What am I doing wrong?

Thanks,

Bill


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

Bill,

On your laptop, after you get the baud rate set, type:

-k

to start kernel-mode debugging. This is also available from the File
pulldown menu.

Start WinDBG on you laptop first, then boot your target machine.

The WinDBG help files are pretty good about explaining this stuff. Worth
the read. The “hang” is probably one of your breakpoints being hit, and
WinDBG is not there to answer the call.

-Evan

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Bill Buchanan
> Sent: Thursday, July 26, 2001 9:25 AM
> To: NT Developers Interest List
> Subject: [ntdev] using windbg - newbie
>
>
> I’m trying to debug for the first time. I compiled and installed
> the mirror
> driver sample and now I want to see what’s going on behind the scenes.
> Since this is my first device driver, I’d like to set breakpoints all over
> the code and watch what’s going on so I can learn.
>


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

Evan’s right. An “extra” tip:

You should also try to connect first with a lower baud rate (e.g.
57600): some low-quality cables doesn’t seem to handle higher
rates than that (I’ve had one). Start with 19200, then if everything
works fine try 38400, then 57600 and then 115200 to check
your cable’s capabilities (57600 is OK most of the times).

(Also, forget about the /debug parameter at boot.ini: it’s not
necessary; it is implicit when you use /debugport and /baudrate)

Miguel Monteiro
xxxxx@criticalsoftware.com

Critical Software, S.A. - http://www.criticalsoftware.com
111 North Market Street, 6th floor, San Jose, CA, USA, 95113
Tel: +1.408.9711231, Fax +1.408.9383929
R. Pedro Nunes, IPN, 3030-199 Coimbra, Portugal
Tel: +351.239.700945 - Fax: +351.239.700905

DISCLAIMER: This mail contents represent
my own personal opinions and do not, in any way,
represent the opinion or policy of Critical Software, S.A.

“Humour and love are God’s answers
to Human weaknesses”

----- Original Message -----
From: “Evan Hillman”
To: “NT Developers Interest List”
Sent: Thursday, July 26, 2001 4:58 PM
Subject: [ntdev] RE: using windbg - newbie

Bill,

On your laptop, after you get the baud rate set, type:

-k

to start kernel-mode debugging. This is also available from the File
pulldown menu.

Start WinDBG on you laptop first, then boot your target machine.

The WinDBG help files are pretty good about explaining this stuff.
Worth
the read. The “hang” is probably one of your breakpoints being hit, and
WinDBG is not there to answer the call.

-Evan

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Bill Buchanan
> Sent: Thursday, July 26, 2001 9:25 AM
> To: NT Developers Interest List
> Subject: [ntdev] using windbg - newbie
>
>
> I’m trying to debug for the first time. I compiled and installed
> the mirror
> driver sample and now I want to see what’s going on behind the scenes.
> Since this is my first device driver, I’d like to set breakpoints all
over
> the code and watch what’s going on so I can learn.
>


You are currently subscribed to ntdev as: xxxxx@criticalsoftware.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

I guess that’s what I don’t understand. What is my “target” machine? My
laptop has the source code and the special entry in boot.ini. What machine
is responsible for what? Also, I haven’t set any breakpoints, I haven’t
gotten that far yet. I think I’m missing one key concept here.

Currently, I have it like this. Source code to driver, windbg, special
boot.ini entry and the driver itself is installed on the laptop. The only
thing I have on my desktop is windbg. So I start windbg on my desktop and
reboot my laptop using the debug entry and never get past the initial boot
sequence. Should I be running windbg on my laptop instead?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Evan Hillman
Sent: Thursday, July 26, 2001 11:58
To: NT Developers Interest List
Subject: [ntdev] RE: using windbg - newbie

Bill,

On your laptop, after you get the baud rate set, type:

-k

to start kernel-mode debugging. This is also available from the File
pulldown menu.

Start WinDBG on you laptop first, then boot your target machine.

The WinDBG help files are pretty good about explaining this stuff. Worth
the read. The “hang” is probably one of your breakpoints being hit, and
WinDBG is not there to answer the call.

-Evan

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Bill Buchanan
> Sent: Thursday, July 26, 2001 9:25 AM
> To: NT Developers Interest List
> Subject: [ntdev] using windbg - newbie
>
>
> I’m trying to debug for the first time. I compiled and installed
> the mirror
> driver sample and now I want to see what’s going on behind the scenes.
> Since this is my first device driver, I’d like to set breakpoints all over
> the code and watch what’s going on so I can learn.
>


You are currently subscribed to ntdev as: xxxxx@connectrf.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

Development machine (your desktop)

Install (in this order):
-VC++ 6.0;
-NTDDK;
-Debugging tools for Windows (WinDbg);
-Your sources (drivers, apps, whatever).

Target machine (your laptop)

-Install nothing but the os and driver(s);
-Set up boot.ini by adding the mentioned entries.

Connect both through serial null-modem cable. Read WinDbg
documentation (debugging help shortcut):
-Using debugging tools for windows>Installation and setup>Kernel-mode
setup

On the development machine, run WinDbg. Start kernel-mode debugging
session (ctrl+k as mentioned). Boot the target machine (your laptop).
Watch
WinDbg’s command window output…

Miguel Monteiro
xxxxx@criticalsoftware.com

Critical Software, S.A. - http://www.criticalsoftware.com
111 North Market Street, 6th floor, San Jose, CA, USA, 95113
Tel: +1.408.9711231, Fax +1.408.9383929
R. Pedro Nunes, IPN, 3030-199 Coimbra, Portugal
Tel: +351.239.700945 - Fax: +351.239.700905

DISCLAIMER: This mail contents represent
my own personal opinions and do not, in any way,
represent the opinion or policy of Critical Software, S.A.

“Humour and love are God’s answers
to Human weaknesses”

----- Original Message -----
From: “Bill Buchanan”
To: “NT Developers Interest List”
Sent: Thursday, July 26, 2001 5:27 PM
Subject: [ntdev] RE: using windbg - newbie

I guess that’s what I don’t understand. What is my “target” machine?
My
laptop has the source code and the special entry in boot.ini. What
machine
is responsible for what? Also, I haven’t set any breakpoints, I haven’t
gotten that far yet. I think I’m missing one key concept here.

Currently, I have it like this. Source code to driver, windbg, special
boot.ini entry and the driver itself is installed on the laptop. The
only
thing I have on my desktop is windbg. So I start windbg on my desktop
and
reboot my laptop using the debug entry and never get past the initial
boot
sequence. Should I be running windbg on my laptop instead?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Evan Hillman
Sent: Thursday, July 26, 2001 11:58
To: NT Developers Interest List
Subject: [ntdev] RE: using windbg - newbie

Bill,

On your laptop, after you get the baud rate set, type:

-k

to start kernel-mode debugging. This is also available from the File
pulldown menu.

Start WinDBG on you laptop first, then boot your target machine.

The WinDBG help files are pretty good about explaining this stuff.
Worth
the read. The “hang” is probably one of your breakpoints being hit, and
WinDBG is not there to answer the call.

-Evan

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Bill Buchanan
> Sent: Thursday, July 26, 2001 9:25 AM
> To: NT Developers Interest List
> Subject: [ntdev] using windbg - newbie
>
>
> I’m trying to debug for the first time. I compiled and installed
> the mirror
> driver sample and now I want to see what’s going on behind the scenes.
> Since this is my first device driver, I’d like to set breakpoints all
over
> the code and watch what’s going on so I can learn.
>


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


You are currently subscribed to ntdev as: xxxxx@criticalsoftware.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

Bill, you are correct, windbg runs on your desktop. In fact, everything
should be on your desktop except the boot.ini mod. It doesn’t hurt to have
the drive source on the target (laptop) but you could lose the source if the
machine crashes and dies. You do need your driver symbols on the host
machine (desktop) if you want to debug so you might as well develop on the
host.

But that’s putting the cart before the horse. Remove your driver and
attempt to establish a debugging session between host and target just to
make sure that works correctly.

BTW, the docs are pretty good; you might want to spend a few minutes reading
them.

–Charles

-----Original Message-----
From: Bill Buchanan [mailto:xxxxx@connectrf.com]
Sent: Thursday, July 26, 2001 12:27 PM
To: NT Developers Interest List
Subject: [ntdev] RE: using windbg - newbie

I guess that’s what I don’t understand. What is my “target” machine? My
laptop has the source code and the special entry in boot.ini. What machine
is responsible for what? Also, I haven’t set any breakpoints, I haven’t
gotten that far yet. I think I’m missing one key concept here.

Currently, I have it like this. Source code to driver, windbg, special
boot.ini entry and the driver itself is installed on the laptop. The only
thing I have on my desktop is windbg. So I start windbg on my desktop and
reboot my laptop using the debug entry and never get past the initial boot
sequence. Should I be running windbg on my laptop instead?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Evan Hillman
Sent: Thursday, July 26, 2001 11:58
To: NT Developers Interest List
Subject: [ntdev] RE: using windbg - newbie

Bill,

On your laptop, after you get the baud rate set, type:

-k

to start kernel-mode debugging. This is also available from the File
pulldown menu.

Start WinDBG on you laptop first, then boot your target machine.

The WinDBG help files are pretty good about explaining this stuff. Worth
the read. The “hang” is probably one of your breakpoints being hit, and
WinDBG is not there to answer the call.

-Evan

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Bill Buchanan
> Sent: Thursday, July 26, 2001 9:25 AM
> To: NT Developers Interest List
> Subject: [ntdev] using windbg - newbie
>
>
> I’m trying to debug for the first time. I compiled and installed
> the mirror
> driver sample and now I want to see what’s going on behind the scenes.
> Since this is my first device driver, I’d like to set breakpoints all over
> the code and watch what’s going on so I can learn.
>


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


You are currently subscribed to ntdev as: xxxxx@xetron.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

Hi Bill,
First obsovation your traget pc should be a machine you can afford to loss
the contents of the hd if the driver go wrong.
So this would not be theone you develop the driver on.
The devlopment pc is know as the host which runs windbg and comunicates with
the target pc which host a version of your driver which you are testing.

Robert Fewrnando

-----Original Message-----
From: Bill Buchanan [mailto:xxxxx@connectrf.com]
Sent: 26 July 2001 17:27
To: NT Developers Interest List
Subject: [ntdev] RE: using windbg - newbie

I guess that’s what I don’t understand. What is my “target” machine? My
laptop has the source code and the special entry in boot.ini. What machine
is responsible for what? Also, I haven’t set any breakpoints, I haven’t
gotten that far yet. I think I’m missing one key concept here.

Currently, I have it like this. Source code to driver, windbg, special
boot.ini entry and the driver itself is installed on the laptop. The only
thing I have on my desktop is windbg. So I start windbg on my desktop and
reboot my laptop using the debug entry and never get past the initial boot
sequence. Should I be running windbg on my laptop instead?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Evan Hillman
Sent: Thursday, July 26, 2001 11:58
To: NT Developers Interest List
Subject: [ntdev] RE: using windbg - newbie

Bill,

On your laptop, after you get the baud rate set, type:

-k

to start kernel-mode debugging. This is also available from the File
pulldown menu.

Start WinDBG on you laptop first, then boot your target machine.

The WinDBG help files are pretty good about explaining this stuff. Worth
the read. The “hang” is probably one of your breakpoints being hit, and
WinDBG is not there to answer the call.

-Evan

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Bill Buchanan
> Sent: Thursday, July 26, 2001 9:25 AM
> To: NT Developers Interest List
> Subject: [ntdev] using windbg - newbie
>
>
> I’m trying to debug for the first time. I compiled and installed
> the mirror
> driver sample and now I want to see what’s going on behind the scenes.
> Since this is my first device driver, I’d like to set breakpoints all over
> the code and watch what’s going on so I can learn.
>


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


You are currently subscribed to ntdev as: xxxxx@anitetelecoms.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

Thanks all for clearing up some of the terminology. The docs do seem to be
well written, but I was tripped up on a few of the meanings (host, target)
and what software should be running where. Now I get it.

One thing I’m concerned about is the fact that I can lose everything. I
can’t afford that luxury on either machine … so I have this question, it
is possible for a device driver to trash all partition tables? Meaning, I
cannot simply install a copy of the OS on a different partition and boot
that when I’m debugging instead of my main OS partition? If not, I’ll have
to find another machine for sure, as I have precious source code on both
machines that I cannot afford to lose (and the code is on a separate
partition from the OS installation).

Thanks again for all of the help.

Bill

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Fernando, Robert
Sent: Thursday, July 26, 2001 13:01
To: NT Developers Interest List
Subject: [ntdev] RE: using windbg - newbie

Hi Bill,
First obsovation your traget pc should be a machine you can afford to loss
the contents of the hd if the driver go wrong.
So this would not be theone you develop the driver on.
The devlopment pc is know as the host which runs windbg and comunicates with
the target pc which host a version of your driver which you are testing.

Robert Fewrnando

-----Original Message-----
From: Bill Buchanan [mailto:xxxxx@connectrf.com]
Sent: 26 July 2001 17:27
To: NT Developers Interest List
Subject: [ntdev] RE: using windbg - newbie

I guess that’s what I don’t understand. What is my “target” machine? My
laptop has the source code and the special entry in boot.ini. What machine
is responsible for what? Also, I haven’t set any breakpoints, I haven’t
gotten that far yet. I think I’m missing one key concept here.

Currently, I have it like this. Source code to driver, windbg, special
boot.ini entry and the driver itself is installed on the laptop. The only
thing I have on my desktop is windbg. So I start windbg on my desktop and
reboot my laptop using the debug entry and never get past the initial boot
sequence. Should I be running windbg on my laptop instead?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Evan Hillman
Sent: Thursday, July 26, 2001 11:58
To: NT Developers Interest List
Subject: [ntdev] RE: using windbg - newbie

Bill,

On your laptop, after you get the baud rate set, type:

-k

to start kernel-mode debugging. This is also available from the File
pulldown menu.

Start WinDBG on you laptop first, then boot your target machine.

The WinDBG help files are pretty good about explaining this stuff. Worth
the read. The “hang” is probably one of your breakpoints being hit, and
WinDBG is not there to answer the call.

-Evan

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Bill Buchanan
> Sent: Thursday, July 26, 2001 9:25 AM
> To: NT Developers Interest List
> Subject: [ntdev] using windbg - newbie
>
>
> I’m trying to debug for the first time. I compiled and installed
> the mirror
> driver sample and now I want to see what’s going on behind the scenes.
> Since this is my first device driver, I’d like to set breakpoints all over
> the code and watch what’s going on so I can learn.
>


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


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


You are currently subscribed to ntdev as: xxxxx@connectrf.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

> Now, I have the source code on my laptop and I also have a line in the

boot.ini like this:
multi(0)disk(0)rdisk(0)partition(2)\WINNT=“Microsoft Windows 2000 Server
(Debug)” /fastdetect /sos /debug /debugport=COM1 /baudrate=115200

Then I run windbg on my desktop and boot the laptop using the boot entry
above. It starts to load drivers and then hangs.

Test you COM port connection. Test the WinDbg’s command line on the desktop.
BTW - you must have sources and symbols on desktop in this environment,
not on laptop, though the cause of the hang is surely not in it.

Max


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

> I guess that’s what I don’t understand. What is my “target” machine? My

Host machine: the one runs WinDbg.
Target machine: the one runs kernel in /debug mode and your driver.

Your problem is nearly surely the COM port hardware problem, try lower baud
rates.

Max


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

Miguel,
Much thanks! That cleared up my confusion. I have a remaining question
about breakpoints. I’m writing a mirror driver and every time I set a
breakpoint in the source, I get the message “Unresolved Breakpoint”. This
happens everytime another driver loads during the boot process. Do I have
to set a hard coded breakpoint for display drivers? There’s no way to load
and unload the driver manually, correct?

Thanks again!

Bill

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Miguel Monteiro
Sent: Thursday, July 26, 2001 12:52
To: NT Developers Interest List
Subject: [ntdev] RE: using windbg - newbie

Development machine (your desktop)

Install (in this order):
-VC++ 6.0;
-NTDDK;
-Debugging tools for Windows (WinDbg);
-Your sources (drivers, apps, whatever).

Target machine (your laptop)

-Install nothing but the os and driver(s);
-Set up boot.ini by adding the mentioned entries.

Connect both through serial null-modem cable. Read WinDbg
documentation (debugging help shortcut):
-Using debugging tools for windows>Installation and setup>Kernel-mode
setup

On the development machine, run WinDbg. Start kernel-mode debugging
session (ctrl+k as mentioned). Boot the target machine (your laptop).
Watch
WinDbg’s command window output…

Miguel Monteiro
xxxxx@criticalsoftware.com

Critical Software, S.A. - http://www.criticalsoftware.com
111 North Market Street, 6th floor, San Jose, CA, USA, 95113
Tel: +1.408.9711231, Fax +1.408.9383929
R. Pedro Nunes, IPN, 3030-199 Coimbra, Portugal
Tel: +351.239.700945 - Fax: +351.239.700905

DISCLAIMER: This mail contents represent
my own personal opinions and do not, in any way,
represent the opinion or policy of Critical Software, S.A.

“Humour and love are God’s answers
to Human weaknesses”

----- Original Message -----
From: “Bill Buchanan”
To: “NT Developers Interest List”
Sent: Thursday, July 26, 2001 5:27 PM
Subject: [ntdev] RE: using windbg - newbie

I guess that’s what I don’t understand. What is my “target” machine?
My
laptop has the source code and the special entry in boot.ini. What
machine
is responsible for what? Also, I haven’t set any breakpoints, I haven’t
gotten that far yet. I think I’m missing one key concept here.

Currently, I have it like this. Source code to driver, windbg, special
boot.ini entry and the driver itself is installed on the laptop. The
only
thing I have on my desktop is windbg. So I start windbg on my desktop
and
reboot my laptop using the debug entry and never get past the initial
boot
sequence. Should I be running windbg on my laptop instead?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Evan Hillman
Sent: Thursday, July 26, 2001 11:58
To: NT Developers Interest List
Subject: [ntdev] RE: using windbg - newbie

Bill,

On your laptop, after you get the baud rate set, type:

-k

to start kernel-mode debugging. This is also available from the File
pulldown menu.

Start WinDBG on you laptop first, then boot your target machine.

The WinDBG help files are pretty good about explaining this stuff.
Worth
the read. The “hang” is probably one of your breakpoints being hit, and
WinDBG is not there to answer the call.

-Evan

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Bill Buchanan
> Sent: Thursday, July 26, 2001 9:25 AM
> To: NT Developers Interest List
> Subject: [ntdev] using windbg - newbie
>
>
> I’m trying to debug for the first time. I compiled and installed
> the mirror
> driver sample and now I want to see what’s going on behind the scenes.
> Since this is my first device driver, I’d like to set breakpoints all
over
> the code and watch what’s going on so I can learn.
>


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


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


You are currently subscribed to ntdev as: xxxxx@connectrf.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

If I have a system that loads a driver at startup, and that driver
repeatedly crashes before I can log in, and I checked the
“System Failure” “Automatically Reboot” box, and I then attach
Windbag, it auto reboots, ignoring the fact that windbag is attached.

Is there a option on windbag that will allow it to stop so I can debug it?
Or get rid of my driver to I can get the system booted so I can look at the
core dump it takes each time?

(I guess I could breakpoint at KeBugCheck, but is there any way to have
Windbag override the system setting for auto reboot?)

Thanks,

-DH


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

Yup. Ctl+Alt+K. Or look at Debug->Kernel Connection->Cycle Initial Break.

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

-----Original Message-----
From: Dave Harvey [mailto:xxxxx@syssoftsol.com]
Sent: Tuesday, July 31, 2001 5:30 PM
To: NT Developers Interest List
Subject: [ntdev] Re: using windbg - newbie

If I have a system that loads a driver at startup, and that driver
repeatedly crashes before I can log in, and I checked the
“System Failure” “Automatically Reboot” box, and I then attach
Windbag, it auto reboots, ignoring the fact that windbag is attached.

Is there a option on windbag that will allow it to stop so I can debug it?
Or get rid of my driver to I can get the system booted so I can look at the
core dump it takes each time?

(I guess I could breakpoint at KeBugCheck, but is there any way to have
Windbag override the system setting for auto reboot?)

Thanks,

-DH


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

Ctl+Alt+K to cause the debugger to break when it first attaches to the
target system. That’s called the “Initial breakpoint”. Set your
breakpoints in your driver, figure out what’s wrong, then fix it. Simple,
hmm? :slight_smile:

-----Original Message-----
From: Dave Harvey [mailto:xxxxx@syssoftsol.com]
Sent: Tuesday, July 31, 2001 5:30 PM
To: NT Developers Interest List
Subject: [ntdev] Re: using windbg - newbie

If I have a system that loads a driver at startup, and that driver
repeatedly crashes before I can log in, and I checked the
“System Failure” “Automatically Reboot” box, and I then attach
Windbag, it auto reboots, ignoring the fact that windbag is attached.

Is there a option on windbag that will allow it to stop so I can debug it?
Or get rid of my driver to I can get the system booted so I can look at the
core dump it takes each time?

(I guess I could breakpoint at KeBugCheck, but is there any way to have
Windbag override the system setting for auto reboot?)

Thanks,

-DH


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