I was so happy to get this configuration up, but I must be missing something. Running target is Win7 x64, host is XP 32. From Windbg I can ‘break’,
but if I can never get it to start again. The target just stays hung while the status on the Windbg "Command - Kernel ‘1394:channel=10’ says BUSY all
the time. It says “Debugee is running…” but I can’t move the mouse or anything. What am I missing?
My apologies. After what seems like a very long time the target will come back to life. I don’t understand what it is doing, but eventually it does
come back. Thanks and sorry for the trouble.
On Sun, 16 Jan 2011 13:49:48 -0800, Michael Wade wrote:
>I was so happy to get this configuration up, but I must be missing something. Running target is Win7 x64, host is XP 32. From Windbg I can ‘break’,
>but if I can never get it to start again. The target just stays hung while the status on the Windbg "Command - Kernel ‘1394:channel=10’ says BUSY all
>the time. It says “Debugee is running…” but I can’t move the mouse or anything. What am I missing?
In my experience long hangs are the pretty common for windbg - (I get hit
about once a week), and its more for 1394 than serial. I have yet to find a
strong linkage but symbol resolution may be a theme and a loaded network
makes it worse.
You probably know this, but you can make you life a lot better (minutes to
maybe 10 to 20 seconds) by making sure that once your symbol store is
populated you keep the remote server off the path. Also make sure that
“Debug->Resolve Unqualified Symbols” is unticked.
Failing that I guess you need to move to Redmond or somewhere electronically
close to msdl.microsoft.com - I cannot believe that the people from MS who
use windbg see these hangs or it would have been fixed…
“Michael Wade” wrote in message news:xxxxx@windbg…
My apologies. After what seems like a very long time the target will come
back to life. I don’t understand
what it is doing, but eventually it does come back. Thanks and sorry for
the trouble.