Message ID | 20241211201739.1380222-1-peterx@redhat.com (mailing list archive) |
---|---|
Headers | show |
Series | scripts/qemu-gdb: Make coroutine dumps to work with coredumps | expand |
Peter Xu <peterx@redhat.com> writes: > Coroutines are used in many cases in block layers. It's also used in live > migration when on destination side, and it'll be handy to diagnose crashes > within a coroutine when we want to also know what other coroutines are > doing. Not sure if you've seen this message on the list: https://lore.kernel.org/r/f0ebccca-7a17-4da8-ac4a-71cf6d69abc3@mtasv.net
On Wed, Dec 11, 2024 at 05:25:10PM -0300, Fabiano Rosas wrote: > Peter Xu <peterx@redhat.com> writes: > > > Coroutines are used in many cases in block layers. It's also used in live > > migration when on destination side, and it'll be handy to diagnose crashes > > within a coroutine when we want to also know what other coroutines are > > doing. > > Not sure if you've seen this message on the list: > > https://lore.kernel.org/r/f0ebccca-7a17-4da8-ac4a-71cf6d69abc3@mtasv.net No I didn't. I only started looking at this because I got a bug a few days ago that I need to look at the main coroutine where dest crashed, then Stefan told me this script and also told me it only works with live session. Ideally I'll need coredump debug-ability, then I figured it isn't too hard. I saw that it didn't yet land gdb, and it's much more involved even if it could be more generic. Not sure how the block developers think, personally I prefer this much smaller change because it works on old systems, where I can easily install gdb with package managers.