Re: [Qemu-devel] Documentation/tools on debuging dyngen code?

["andrzej zaborowski" <balrogg@gmail.com>]

2008/10/1 Bruce Beare (bbeare) <bbeare@cisco.com>:
> I'm working on a 2.6.24 Linux port built for ARCH=powerpc and configured
> for the PReP machine. I have the port booting using an unmodified 0.9.1
> version (actually, head from the SVN repo) of qemu-system-ppc but
> sometimes find that QEMU "hangs". Analysis of the hang reveals:
>
>  o C-A C-X does not respond
>  o QEMU is sucking up 100% cpu time of one processor
>  o GDB to the kernel debug port (qemu option -s -p 1234) is non
> responsive
>  o ltrace, strace show no system or library calls in progress
>  o GDB on QEMU shows that it is executing apparently valid code in the
> 0x4xxxxxxx
>    range.
>
> My conclusion is that QEMU is looping while executing the dynamically
> generated code. I'd like to debug this further... and am looking for
> some pointers on how to do so. Is there a built-in debugger? Is there a

I'm seeing a similar lock-up since around the time of the conversion
to TCG.  It's caused by an interrupt being lost for some reason (a
signal not causing an exit from cpu loop properly).  I've hit it on an
ARM target and Daniel Jacobowitz reproduced it on an x86 target).  If
what you see is the same problem, adding -clock unix manages to work
around it because it means that signals will keep coming even if one
is lost and eventually the cpu loop will end, but this isn't a proper
fix.

Cheers