From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@redhat.com
Subject: [Qemu-devel] [PATCH 0/3] qemu-gdb: add functionality for inspecting core dumps
Date: Mon, 12 Oct 2015 10:02:51 +0200 [thread overview]
Message-ID: <1444636974-19950-1-git-send-email-pbonzini@redhat.com> (raw)
Currently it is very hard to inspect coroutine in core dumps, because
none of the qemu-gdb functionality works. Fixing this is not really
possible because "bt" only works on the core dump's stack pointer and
program counter, but the situation would improve noticeably if only
a coroutine's stack pointer and program counter were accessible at all;
that would allow inspecting the coroutine's stack and building a
stack trace from the hex dump of the stack.
The main hurdle is that glibc_pointer_guard() cannot be run on a core
dump, because get_fs_base() uses the arch_prctl system call. The first
patch modifies that to use the gdb API instead. The second and third
patch then add the new functions.
Paolo
Paolo Bonzini (3):
qemu-gdb: allow using glibc_pointer_guard() on core dumps
qemu-gdb: extract parts of "qemu coroutine" implementation
qemu-gdb: add $qemu_coroutine_sp and $qemu_coroutine_pc
scripts/qemu-gdb.py | 3 ++
scripts/qemugdb/coroutine.py | 90 +++++++++++++++++++++++++++++---------------
2 files changed, 62 insertions(+), 31 deletions(-)
--
2.5.0
next reply other threads:[~2015-10-12 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 8:02 Paolo Bonzini [this message]
2015-10-12 8:02 ` [Qemu-devel] [PATCH 1/3] qemu-gdb: allow using glibc_pointer_guard() on core dumps Paolo Bonzini
2015-10-12 8:02 ` [Qemu-devel] [PATCH 2/3] qemu-gdb: extract parts of "qemu coroutine" implementation Paolo Bonzini
2015-10-12 8:02 ` [Qemu-devel] [PATCH 3/3] qemu-gdb: add $qemu_coroutine_sp and $qemu_coroutine_pc Paolo Bonzini
2015-10-13 10:14 ` [Qemu-devel] [PATCH 0/3] qemu-gdb: add functionality for inspecting core dumps 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=1444636974-19950-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).