From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH] scripts/qemugdb: support coroutine backtrace in coredumps
Date: Wed, 4 Apr 2018 11:34:40 +0100 [thread overview]
Message-ID: <20180404103440.19546-1-stefanha@redhat.com> (raw)
Use the 'select-frame' GDB command to switch stacks instead of manually
setting the debugged thread's registers (this only works when debugging
a live process, not in a coredump).
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
Vladimir: Does this work for you?
scripts/qemugdb/coroutine.py | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/scripts/qemugdb/coroutine.py b/scripts/qemugdb/coroutine.py
index ab699794ab..ed96434aee 100644
--- a/scripts/qemugdb/coroutine.py
+++ b/scripts/qemugdb/coroutine.py
@@ -77,13 +77,11 @@ def bt_jmpbuf(jmpbuf):
for i in regs:
old[i] = gdb.parse_and_eval('(uint64_t)$%s' % i)
- for i in regs:
- gdb.execute('set $%s = %s' % (i, regs[i]))
+ gdb.execute('select-frame %s %s' % (regs['rsp'], regs['rip']))
gdb.execute('bt')
- for i in regs:
- gdb.execute('set $%s = %s' % (i, old[i]))
+ gdb.execute('select-frame %s %s' % (old['rsp'], old['rip']))
def coroutine_to_jmpbuf(co):
coroutine_pointer = co.cast(gdb.lookup_type('CoroutineUContext').pointer())
--
2.14.3
next reply other threads:[~2018-04-04 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 10:34 Stefan Hajnoczi [this message]
2018-04-09 13:01 ` [Qemu-devel] [PATCH] scripts/qemugdb: support coroutine backtrace in coredumps Vladimir Sementsov-Ogievskiy
2018-04-10 2:08 ` Stefan Hajnoczi
2018-04-23 1:37 ` Simon Marchi
2018-04-23 9:33 ` Stefan Hajnoczi
2018-04-23 9:48 ` Vladimir Sementsov-Ogievskiy
2018-04-23 13:28 ` Pedro Alves
2018-12-27 17:36 ` Vladimir Sementsov-Ogievskiy
2019-01-02 14:01 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180404103440.19546-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).