cannot talk to windbg/target ?

Using windbg 6.7.5.1

I am trying to debug in kernel mode a windows xp sp3 computer (32 bit). amd
athlon 64 x2 dual 3800+
I have established serial communication with the target and proved it with
hyperterminal.

I put the /sos switch on in the boot.ini file so I can verify that I am
really going into debug mode, the target spews drivers as expected.
Furthermore, I have run a test program that calls DebugBreak() from user
mode and it locks up the machine…

I can conclude that this machine thinks it is in debug mode.

YET, I CANNOT CAUSE GET WINDBG TO TALK WITH THE MACHINE:

When windbg is running and I reboot the machine I don’t get the normal spew.
Control Break does not break into the other machine.

What can possibly be the matter?

xxxxx@sbcglobal.net wrote:

Using windbg 6.7.5.1

I am trying to debug in kernel mode a windows xp sp3 computer (32 bit). amd
athlon 64 x2 dual 3800+
I have established serial communication with the target and proved it with
hyperterminal.

I put the /sos switch on in the boot.ini file so I can verify that I am
really going into debug mode, the target spews drivers as expected.
Furthermore, I have run a test program that calls DebugBreak() from user
mode and it locks up the machine…

I can conclude that this machine thinks it is in debug mode.

YET, I CANNOT CAUSE GET WINDBG TO TALK WITH THE MACHINE:

When windbg is running and I reboot the machine I don’t get the normal spew.
Control Break does not break into the other machine.

What can possibly be the matter?

The most common issue is that the COM port and speed you used in
Hyperterminal do not match the ones you have in your boot.ini command
line and in the Windbg kernel debug options.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

As Tim already mentioned, it would be a good idea to double check that your windbg settings match
your boot.ini settings. To that end, posting both (boot.ini line and windbg command line) would at
least help rule out the simple problems.

Otherwise, I don’t recall when the problem surfaced and when it disappeared, but 6.7.5.1 might fall
in to the range of windbg versions that I found would ‘lock’ the machine, but not cause windbg to
break in if either of two were true:

  1. if ‘-b’ was used on the command line; I think that ‘-d’ had the same problem, but I can’t
    remember for sure.

  2. if /halbreakpoint was set using bcdedit

Now this was obviously for a Vista target, but perhaps it was also true for xp with ‘/break’ added
to the boot.ini of the target.

I don’t think that this is likely your problem, but it might be worth a look.

Good luck,

mm

Tim Roberts wrote:

xxxxx@sbcglobal.net wrote:
> Using windbg 6.7.5.1
>
> I am trying to debug in kernel mode a windows xp sp3 computer (32 bit). amd
> athlon 64 x2 dual 3800+
> I have established serial communication with the target and proved it with
> hyperterminal.
>
> I put the /sos switch on in the boot.ini file so I can verify that I am
> really going into debug mode, the target spews drivers as expected.
> Furthermore, I have run a test program that calls DebugBreak() from user
> mode and it locks up the machine…
>
> I can conclude that this machine thinks it is in debug mode.
>
> YET, I CANNOT CAUSE GET WINDBG TO TALK WITH THE MACHINE:
>
> When windbg is running and I reboot the machine I don’t get the normal spew.
> Control Break does not break into the other machine.
>
> What can possibly be the matter?
>

The most common issue is that the COM port and speed you used in
Hyperterminal do not match the ones you have in your boot.ini command
line and in the Windbg kernel debug options.

In addition to the other responses you might look at device manager and make
sure your serial port is using the standard port and IRQ addresses for the
serial port. Anything other than COM1 or COM2 usually will not work.
Mixing the wrong port address with the wrong IRQ could cause problems that
hyperterminal might not see.

wrote in message news:xxxxx@windbg…
>
> Using windbg 6.7.5.1
>
> I am trying to debug in kernel mode a windows xp sp3 computer (32 bit).
> amd
> athlon 64 x2 dual 3800+
> I have established serial communication with the target and proved it with
> hyperterminal.
>
> I put the /sos switch on in the boot.ini file so I can verify that I am
> really going into debug mode, the target spews drivers as expected.
> Furthermore, I have run a test program that calls DebugBreak() from user
> mode and it locks up the machine…
>
> I can conclude that this machine thinks it is in debug mode.
>
> YET, I CANNOT CAUSE GET WINDBG TO TALK WITH THE MACHINE:
>
> When windbg is running and I reboot the machine I don’t get the normal
> spew.
> Control Break does not break into the other machine.
>
> What can possibly be the matter?
>
>
>