Issue on setting up WinDbg in Win2k

NTDEV
1

Hello everyone:

I want to set up a WinDbg environment. I installed Windows 2000
Professional Free version and service pack 1 in both development and target
machines. According to the documents, I have changed boot.ini file in
target machine and restarted it, and also I run WinDbg in the development
machine. However, the target machine stoped at the time when system
restarts, in the meantime, WinDbg displayed the following information.

Since this is the first time for me to use WinDbg, I don’t know what
happened? Could anyone give me some suggestion or correct ways to set up
WinDbg?

Thank you for your help in advance!

Followed is the information displyed in WinDbg window:

Symbol search path is: d:\winnt\symbols
Opened \.\COM1

Microsoft (R) Windows Kernel Debugger
Version 3.0.0007.0
Copyright (c) Microsoft Corporation. All rights reserved.

Waiting to reconnect…
Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Loaded dbghelp extension DLL
Loaded ext extension DLL
Loaded kext extension DLL
Loaded kdextx86 extension DLL
Symbol search path is: d:\winnt\symbols
Executable search path is:
PsLoadedModuleList not initialized yet. Delay kernel load.
Windows 2000 Kernel Version 2195 UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046b618

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

maybe you have set the intial break point!!!
it’s ok

You can trace into the target machine or you can let it continue booting
normally

johnny

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of
xxxxx@asia.adaptec.com
Sent: Monday, April 23, 2001 1:32 AM
To: NT Developers Interest List
Subject: [ntdev] Issue on setting up WinDbg in Win2k

Hello everyone:

I want to set up a WinDbg environment. I installed Windows 2000
Professional Free version and service pack 1 in both development and target
machines. According to the documents, I have changed boot.ini file in
target machine and restarted it, and also I run WinDbg in the development
machine. However, the target machine stoped at the time when system
restarts, in the meantime, WinDbg displayed the following information.

Since this is the first time for me to use WinDbg, I don’t know what
happened? Could anyone give me some suggestion or correct ways to set up
WinDbg?

Thank you for your help in advance!

Followed is the information displyed in WinDbg window:

Symbol search path is: d:\winnt\symbols
Opened \.\COM1

Microsoft (R) Windows Kernel Debugger
Version 3.0.0007.0
Copyright (c) Microsoft Corporation. All rights reserved.

Waiting to reconnect…
Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Loaded dbghelp extension DLL
Loaded ext extension DLL
Loaded kext extension DLL
Loaded kdextx86 extension DLL
Symbol search path is: d:\winnt\symbols
Executable search path is:
PsLoadedModuleList not initialized yet. Delay kernel load.
Windows 2000 Kernel Version 2195 UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046b618

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

Do You Yahoo!?

Get your free @yahoo.com address at http://mail.yahoo.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

3

> machine. However, the target machine stoped at the time when system

restarts, in the meantime, WinDbg displayed the following information.
Check whether the Debug->Go option is enabled on the host machine windbg.
If it is enabled, click Go or press F5.

-Aparna

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

4

Hi, Aparna,

Debug->Go option is disabled. Any other idea?

Thanks!
Shunnian

On 04/23/01, ““Aparna Sachin Argade” ” wrote:
> > machine. However, the target machine stoped at the time when system
> > restarts, in the meantime, WinDbg displayed the following information.
> Check whether the Debug->Go option is enabled on the host machine windbg.
> If it is enabled, click Go or press F5.
>
> -Aparna
>
>
> —
> 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

—
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

5

Hi, johnny,

I didn’t find the setting for the intial break point in WinDbg version
3.0.0007.0, while I notice there is this setting in WinDbg provided in SDK
tools. Any further idea for my issue?

Thanks!
Shunnian

On 04/23/01, ““Johnny Habibi” ” wrote:
> maybe you have set the intial break point!!!
> it’s ok
>
> You can trace into the target machine or you can let it continue booting
> normally
>
>
> johnny
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of
> xxxxx@asia.adaptec.com
> Sent: Monday, April 23, 2001 1:32 AM
> To: NT Developers Interest List
> Subject: [ntdev] Issue on setting up WinDbg in Win2k
>
>
> Hello everyone:
>
> I want to set up a WinDbg environment. I installed Windows 2000
> Professional Free version and service pack 1 in both development and target
> machines. According to the documents, I have changed boot.ini file in
> target machine and restarted it, and also I run WinDbg in the development
> machine. However, the target machine stoped at the time when system
> restarts, in the meantime, WinDbg displayed the following information.
>
> Since this is the first time for me to use WinDbg, I don’t know what
> happened? Could anyone give me some suggestion or correct ways to set up
> WinDbg?
>
> Thank you for your help in advance!
>
> Followed is the information displyed in WinDbg window:
>
> Symbol search path is: d:\winnt\symbols
> Opened \.\COM1
>
> Microsoft (R) Windows Kernel Debugger
> Version 3.0.0007.0
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Waiting to reconnect…
> Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
> Kernel Debugger connection established.
> Loaded dbghelp extension DLL
> Loaded ext extension DLL
> Loaded kext extension DLL
> Loaded kdextx86 extension DLL
> Symbol search path is: d:\winnt\symbols
> Executable search path is:
> PsLoadedModuleList not initialized yet. Delay kernel load.
> Windows 2000 Kernel Version 2195 UP Free x86 compatible
> Kernel base = 0x80400000 PsLoadedModuleList = 0x8046b618
>
> —
> You are currently subscribed to ntdev as: xxxxx@yahoo.de
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
>
> _________________________________________________________
>
> Do You Yahoo!?
>
> Get your free @yahoo.com address at http://mail.yahoo.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

—
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

6

Try setting your baudrate to 19200 on both development and
target machines. If it works, then you could try upwards
for 38400, 57600 or 115200.

Niraj

-----Original Message-----
From: xxxxx@asia.adaptec.com [mailto:xxxxx@asia.adaptec.com]
Sent: Sunday, April 22, 2001 6:32 PM
To: NT Developers Interest List
Subject: [ntdev] Issue on setting up WinDbg in Win2k

Hello everyone:

I want to set up a WinDbg environment. I installed Windows 2000
Professional Free version and service pack 1 in both development and target
machines. According to the documents, I have changed boot.ini file in
target machine and restarted it, and also I run WinDbg in the development
machine. However, the target machine stoped at the time when system
restarts, in the meantime, WinDbg displayed the following information.

Since this is the first time for me to use WinDbg, I don’t know what
happened? Could anyone give me some suggestion or correct ways to set up
WinDbg?

Thank you for your help in advance!

Followed is the information displyed in WinDbg window:

Symbol search path is: d:\winnt\symbols
Opened \.\COM1

Microsoft (R) Windows Kernel Debugger
Version 3.0.0007.0
Copyright (c) Microsoft Corporation. All rights reserved.

Waiting to reconnect…
Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Loaded dbghelp extension DLL
Loaded ext extension DLL
Loaded kext extension DLL
Loaded kdextx86 extension DLL
Symbol search path is: d:\winnt\symbols
Executable search path is:
PsLoadedModuleList not initialized yet. Delay kernel load.
Windows 2000 Kernel Version 2195 UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046b618

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

7

All is correct, I always see such prints.

----- Original Message -----
From:
To: “NT Developers Interest List”
Sent: Monday, April 23, 2001 1:32 AM
Subject: [ntdev] Issue on setting up WinDbg in Win2k

> Hello everyone:
>
> I want to set up a WinDbg environment. I installed Windows 2000
> Professional Free version and service pack 1 in both development and
target
> machines. According to the documents, I have changed boot.ini file in
> target machine and restarted it, and also I run WinDbg in the development
> machine. However, the target machine stoped at the time when system
> restarts, in the meantime, WinDbg displayed the following information.
>
> Since this is the first time for me to use WinDbg, I don’t know what
> happened? Could anyone give me some suggestion or correct ways to set up
> WinDbg?
>
> Thank you for your help in advance!
>
> Followed is the information displyed in WinDbg window:
>
> Symbol search path is: d:\winnt\symbols
> Opened \.\COM1
>
> Microsoft (R) Windows Kernel Debugger
> Version 3.0.0007.0
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Waiting to reconnect…
> Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
> Kernel Debugger connection established.
> Loaded dbghelp extension DLL
> Loaded ext extension DLL
> Loaded kext extension DLL
> Loaded kdextx86 extension DLL
> Symbol search path is: d:\winnt\symbols
> Executable search path is:
> PsLoadedModuleList not initialized yet. Delay kernel load.
> Windows 2000 Kernel Version 2195 UP Free x86 compatible
> Kernel base = 0x80400000 PsLoadedModuleList = 0x8046b618
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.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

8

Trying 19200 is the best thing to do at first.
If the debugger continues to show you the same output, with no prompt, and
the target machine is hung, then there is a communication problem between
the two machines.
Try typing ctrl-alt-r and then Ctrl-break, see if helps to wake up
the communication.
You can also try changing cables or using a different COM port.

-Andre

—
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

9

Hello all:

Thanks for your help. I have tried 19200 and it works very well, but the
speed is rather slow both in debugger and debuggee. Then I tried 38400,
57600 and 115200, but they all failed. I don’t know why?

I use HyperTerminal to test 57600 and 115200, they all worked very well, so
it shows my COM1 connection is right.

Any further good suggestion?

Thanks in advance!

Shunnian

On 04/23/01, “xxxxx@microsoft.com” wrote:

Trying 19200 is the best thing to do at first.
If the debugger continues to show you the same output, with no prompt, and
the target machine is hung, then there is a communication problem between
the two machines.
Try typing ctrl-alt-r and then Ctrl-break, see if helps to wake up
> the communication.
> You can also try changing cables or using a different COM port.
>
> -Andre
>
> —
> 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

—
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

10

How much data are you sending with hyperterminal ? A few bytes ?

The debugger can sometimes send up to 4K at a time over the wire. My guess
is you just have poor COM ports or a poor wire that does not handle higher
speeds as well.

-Andre

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

11

I might be guessing, but maybe Shunnian’s problem is just a
matter of setting ‘/baudrate=57600’ on boot.ini file at the target
machine, before trying to establish connection at 57600 from
the host… :slight_smile:

Miguel Monteiro
xxxxx@criticalsoftware.com
www.criticalsoftware.com

«Humour and love are God’s answers
to Human weaknesses»

----- Original Message -----
From:
To: “NT Developers Interest List”
Sent: Monday, April 23, 2001 10:30 PM
Subject: [ntdev] RE: Issue on setting up WinDbg in Win2k

Hello all:

Thanks for your help. I have tried 19200 and it works very well, but the
speed is rather slow both in debugger and debuggee. Then I tried 38400,
57600 and 115200, but they all failed. I don’t know why?

I use HyperTerminal to test 57600 and 115200, they all worked very well,
so
it shows my COM1 connection is right.

Any further good suggestion?

Thanks in advance!

Shunnian

On 04/23/01, “xxxxx@microsoft.com” wrote:
> Trying 19200 is the best thing to do at first.
> If the debugger continues to show you the same output, with no prompt,
and
> the target machine is hung, then there is a communication problem
between
> the two machines.
> Try typing ctrl-alt-r and then Ctrl-break, see if helps to
wake up
> the communication.
> You can also try changing cables or using a different COM port.
>
> -Andre

—
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

12

Hi, Miguel,

Actually, I have done it. Any idea?

Thanks!
Shunnian

On 04/24/01, ““Miguel Monteiro” ” wrote:
> I might be guessing, but maybe Shunnian’s problem is just a
> matter of setting ‘/baudrate=57600’ on boot.ini file at the target
> machine, before trying to establish connection at 57600 from
> the host… :slight_smile:
>
> Miguel Monteiro
> xxxxx@criticalsoftware.com
> www.criticalsoftware.com
> ------------------------------------------------------------
> «Humour and love are God’s answers
> to Human weaknesses»
> ------------------------------------------------------------
>
> ----- Original Message -----
> From:
> To: “NT Developers Interest List”
> Sent: Monday, April 23, 2001 10:30 PM
> Subject: [ntdev] RE: Issue on setting up WinDbg in Win2k
>
>
> Hello all:
>
> Thanks for your help. I have tried 19200 and it works very well, but the
> speed is rather slow both in debugger and debuggee. Then I tried 38400,
> 57600 and 115200, but they all failed. I don’t know why?
>
> I use HyperTerminal to test 57600 and 115200, they all worked very well,
> so
> it shows my COM1 connection is right.
>
> Any further good suggestion?
>
> Thanks in advance!
>
> Shunnian
>
> On 04/23/01, “xxxxx@microsoft.com” wrote:
> > Trying 19200 is the best thing to do at first.
> > If the debugger continues to show you the same output, with no prompt,
> and
> > the target machine is hung, then there is a communication problem
> between
> > the two machines.
> > Try typing ctrl-alt-r and then Ctrl-break, see if helps to
> wake up
> > the communication.
> > You can also try changing cables or using a different COM port.
> >
> > -Andre
>
>
>
> —
> 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

—
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

13

Hi, Andre,

Yes, you are right, I only try to send a few bytes with keyboard in
hyperterminal.

As for your guess that I have poor COM ports, I don’t agree with you,
because my two PCs are all quite new, one is PIII-866 and another is
PIII-733. However, I am not sure if my null-modem cable is good enough,
maybe I should change another one to try. BTW, can you tell me what is the
best and maximum transfer speed setting in WinDbg, if all hardwares are
good enough to support them.

Thanks for your help!

Shunnian

On 04/24/01, “xxxxx@microsoft.com” wrote:

How much data are you sending with hyperterminal ? A few bytes ?

The debugger can sometimes send up to 4K at a time over the wire. My guess
is you just have poor COM ports or a poor wire that does not handle higher
speeds as well.

-Andre

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

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

14

COM port reliability has nothing to do with how fast or new the machine is.
We’ve actually had a number of new machines, 1 Ghz and up, where serial
communication did not work well at higher baudrates. They only worked
reliably at 19200. We have no clue why.

You can go up to 115200 on many machines - but again, it depends on the
hardware you have.

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

15

Hi, Andre,

Thank you for your further explanation. Therefore, we have to do some tests
to see which baudrate can be reliably used in our system every time when we
set up a new WinDbg debug environment.

Thanks again for your help!

Shunnian

On 04/25/01, “xxxxx@microsoft.com” wrote:

COM port reliability has nothing to do with how fast or new the machine is.
We’ve actually had a number of new machines, 1 Ghz and up, where serial
communication did not work well at higher baudrates. They only worked
reliably at 19200. We have no clue why.

You can go up to 115200 on many machines - but again, it depends on the
hardware you have.

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

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

16

Actually, no. :slight_smile: My guess is Andre Vachon has a point and your
problem might be in a low-quality cable (rather than low-quality
COM ports). Check the Debugging Tools for Windows documentation,
on:

Installation and Setup>Kernel-Mode Setup>Configuring Hardware for
Kernel-Mode Debugging>Setting Up a Null-modem Cable connection

to find a complete description of how the cable connections should be
done
(check also the tip near the end, it might be useful).

Hope it helps,

Miguel Monteiro
xxxxx@criticalsoftware.com
www.criticalsoftware.com

«Humour and love are God’s answers
to Human weaknesses»

----- Original Message -----
From:
To: “NT Developers Interest List”
Sent: Tuesday, April 24, 2001 8:48 PM
Subject: [ntdev] RE: Issue on setting up WinDbg in Win2k

Hi, Miguel,

Actually, I have done it. Any idea?

Thanks!
Shunnian

On 04/24/01, ““Miguel Monteiro” ” wrote:
> I might be guessing, but maybe Shunnian’s problem is just a
> matter of setting ‘/baudrate=57600’ on boot.ini file at the target
> machine, before trying to establish connection at 57600 from
> the host… :slight_smile:
>
> Miguel Monteiro
> xxxxx@criticalsoftware.com
> www.criticalsoftware.com
> ------------------------------------------------------------
> «Humour and love are God’s answers
> to Human weaknesses»
> ------------------------------------------------------------
>
> ----- Original Message -----
> From:
> To: “NT Developers Interest List”
> Sent: Monday, April 23, 2001 10:30 PM
> Subject: [ntdev] RE: Issue on setting up WinDbg in Win2k
>
>
> Hello all:
>
> Thanks for your help. I have tried 19200 and it works very well, but
the
> speed is rather slow both in debugger and debuggee. Then I tried
38400,
> 57600 and 115200, but they all failed. I don’t know why?
>
> I use HyperTerminal to test 57600 and 115200, they all worked very
well,
> so
> it shows my COM1 connection is right.
>
> Any further good suggestion?
>
> Thanks in advance!
>
> Shunnian
>
> On 04/23/01, “xxxxx@microsoft.com” wrote:
> > Trying 19200 is the best thing to do at first.
> > If the debugger continues to show you the same output, with no
prompt,
> and
> > the target machine is hung, then there is a communication problem
> between
> > the two machines.
> > Try typing ctrl-alt-r and then Ctrl-break, see if helps to
> wake up
> > the communication.
> > You can also try changing cables or using a different COM port.
> >
> > -Andre

—
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