Collecting information from a hung qemu process

[Richard W.M. Jones]

I filed this bug about recent Linux hanging very rarely when booting
on recent qemu:

https://gitlab.com/qemu-project/qemu/-/issues/1696

As I'm able to reproduce this bug at will (albeit I have to wait for
100s or 1000s of iterations of the test), I am able to observe the
qemu process after it hangs.  Is there any information which is useful
to collect from the hung qemu, such as stack traces, etc?

I know how to collect a stack trace, but if there's other information
please give me a guide about how to collect that.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW