From: Richard Henderson <rth@twiddle.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v2] Use the GDB JIT debugging interface
Date: Mon, 19 Mar 2012 12:25:10 -0700 [thread overview]
Message-ID: <1332185111-20739-1-git-send-email-rth@twiddle.net> (raw)
I was reminded about this from a comment on the list, where
a new developer had gotten confused by our backtrace.
Changes from V1 to V2:
* Rebase to master.
* Do not try to allocate the ELF stuff within the code_gen_buffer.
Instead we can use a SHT_NOBITS trick to say that's out-of-line.
* Use C structures (with alignment and packing annotations) to create
the Dwarf2 unwind info. Previously I had used inline assembly.
Example:
Breakpoint 1, helper_idivl_EAX (t0=512)
at /home/rth/work/qemu/qemu/target-i386/op_helper.c:1882
1882 {
(gdb) where
#0 helper_idivl_EAX (t0=512)
at /home/rth/work/qemu/qemu/target-i386/op_helper.c:1882
#1 0x00005555557c0fdf in static_code_gen_buffer ()
#2 0x000055555559714d in cpu_x86_exec (env=0x5555577fba30)
at /home/rth/work/qemu/qemu/cpu-exec.c:564
#3 0x00005555555b3290 in cpu_loop (env=0x5555577fba30)
at /home/rth/work/qemu/qemu/linux-user/main.c:317
#4 0x00005555555b40a4 in main (argc=<optimized out>, argv=<optimized out>,
envp=<optimized out>) at /home/rth/work/qemu/qemu/linux-user/main.c:3826
r~
Richard Henderson (1):
tcg: Use the GDB JIT debugging interface.
elf.h | 1 +
exec.c | 1 +
tcg/i386/tcg-target.c | 114 ++++++++++++++++++++++++++--
tcg/tcg.c | 194 +++++++++++++++++++++++++++++++++++++++++++++++++
tcg/tcg.h | 2 +
5 files changed, 303 insertions(+), 9 deletions(-)
--
1.7.7.6
next reply other threads:[~2012-03-19 19:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 19:25 Richard Henderson [this message]
2012-03-19 19:25 ` [Qemu-devel] [PATCH] tcg: Use the GDB JIT debugging interface Richard Henderson
2012-03-24 16:11 ` Blue Swirl
2012-03-24 17:04 ` Peter Maydell
2012-03-19 20:08 ` [Qemu-devel] [PATCH v2] " Peter Maydell
2012-03-19 20:48 ` Richard Henderson
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=1332185111-20739-1-git-send-email-rth@twiddle.net \
--to=rth@twiddle.net \
--cc=qemu-devel@nongnu.org \
/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).