Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

windbg 6.12 fails to break over serial connection

14 views
Skip to first unread message

Pavel A.

unread,
Mar 12, 2010, 4:52:42 PM3/12/10
to
After xcopy installing windbg 6.12 on a development machine that has v 6.11,
I've noticed that 6.12 often fails to break into a debuggee over serial
cable,
while 6.11 on exactly same setup breaks quickly and reliably.
After restarting v. 6.12, break in works.

It's pity, but I don't work on win8 beta yet; my targets are old rusty XP
and 2003 x86.
Does anybody test new windbg releases for regression agains these targets?

Regards,.
--pa

Andreas

unread,
Apr 13, 2010, 6:19:01 AM4/13/10
to
I have the exact same problem, the WinDbg does not break into the target. The
target PC freezes, but the debugger seems to not get the answer. It just does
not react at all. After that, you can only reboot the target PC.
(Last Version that worked with this target is 6.11, target runs XP SP3.)

Pavel A.

unread,
Apr 13, 2010, 7:47:28 PM4/13/10
to
Thanks for confirming.
--pa

"Andreas" <And...@discussions.microsoft.com> wrote in message
news:B4433FD4-7375-4CFB...@microsoft.com...

Pavel Lebedinsky [MSFT]

unread,
Apr 14, 2010, 2:32:14 AM4/14/10
to
>I have the exact same problem, the WinDbg does not break into the target.
>The
> target PC freezes, but the debugger seems to not get the answer. It just
> does
> not react at all. After that, you can only reboot the target PC.
> (Last Version that worked with this target is 6.11, target runs XP SP3.)

I think I've seen something similar with recent debugger builds. Ctrl+C
would freeze the target but no output would appear in kd. The first
few times this happened I had to reboot the target, but the last time
I accidentally typed some command ('r' or something like that)
followed by Enter, and suddenly the usual debugger output, including
the breakin message and the prompt, appeared. I haven't been able
to reproduce the problem since then so I don't know if entering a
command always works.

--
Pavel Lebedinsky/Windows Fundamentals Test
This posting is provided "AS IS" with no warranties, and confers no rights.


Gernot Buselmeier

unread,
Apr 21, 2010, 10:11:02 AM4/21/10
to
I have a similar observation but slighly different, and not related to
WinDbg 6.12.
Hence, I will open a separate thread here: "Losing connection to Debug
Kernel".

GB

0 new messages