firewire + windbg == unstable?

I just started debugging over a firewire connection a few days ago, and
I am seeing alot of problems when stepping through source code… It
seems like the debugger gets out of sync with the target machine and
starts spitting out a bunch of messages like:

DbgKdReadVirtualMemoryNow: Asked for 128, got 256
Unable to read KTHREAD address ffa596c4
DbgKdReadVirtualMemoryNow: Asked for 101, got 128
DbgKdReadVirtualMemoryNow: Asked for 27, got 128
DbgKdReadVirtualMemoryNow: Asked for 101, got 128
DbgKdReadVirtualMemoryNow: Asked for 27, got 128
DbgKdReadVirtualMemoryNow: Asked for 101, got 128
DbgKdReadVirtualMemoryNow: Asked for 27, got 128
DbgKdReadVirtualMemoryNow: Asked for 101, got 128
DbgKdReadVirtualMemoryNow: Asked for 27, got 128
DbgKdReadVirtualMemoryNow: Asked for 101, got 128
DbgKdReadVirtualMemoryNow: Asked for 27, got 128
DbgKdReadVirtualMemoryNow: Asked for 101, got 128
DbgKdReadVirtualMemoryNow: Asked for 27, got 128
DbgKdReadVirtualMemoryNow: Asked for 101, got 128
Unable to read KTHREAD address ffa596c4
Unable to read KTHREAD address ffa596c4
Unable to read KTHREAD address ffa596c4
Unable to read KTHREAD address ffa596c4
kd> p
KD: Attempt to set breakpoint bf9c4fb7 twice!

Usually this requires me to restart WinDBG… sometimes I can hit
ctrl-break again in the same session and try and walk out of the
problem, but it usually just gets worse. Also it seems like this
sometimes causes the firewire driver to get out of state and require a
reboot of the host, the target, or both (although this could be a buggy
firewire card i guess)…

Has anyone else seen this or is this a known bug with debugging over
firewire? I am using XP RC2 on both machines so that may be a source of
the problem… but I never saw the problem when using a serial
connection.

The windbg version I am using is the latest available - 4.0.0011.0

Thanks,
sean


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

This is a know problem with the 1394 debugger wire protocol, and it
unfortunately requires OS changes to fix. The fix is available in Windows
.NET BETA 3 and will be in Windows XP SP1.

-Andre


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