On 05/12/2017 09:37 AM, Stefan Hajnoczi wrote: > From: "Daniel P. Berrange" <berra...@redhat.com> > > The GThread implementation is not functional enough to actually > run QEMU reliably. While it was potentially useful for debugging, > we have a scripts/qemugdb/coroutine.py to enable tracing of > ucontext coroutines in GDB, so that removes the only reason for > GThread to exist. >
Quick question (unrelated to the pull request): Can we get a patch to scripts/qemugdb/coroutine.py or nearby that mentions the preferred way to actually use the script? I didn't know the script existed before seeing this commit message, and was sad to see that it was not self-documenting (or else a scripts/qemugdb/README file) on how best to utilize the script (is it as simple as running 'gdb --some-arg /path/to/coroutine.py'? do you have to install some magic file to tell gdb to autoload the file any time you are debugging qemu? something else???). Okay, I searched a bit harder, and found that scripts/qemu-gdb.py loads these subscripts, if you type 'source scripts/qemu-gdb.py' at the (gdb) prompt. Still, is there a way to automate that so that the scripts are loaded every time you fire up gdb, instead of having to remember to do it by hand? And if so, can that be documented? -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
