From: Daniel Jacobowitz <drow@false.org>
To: Richard Henderson <rth@twiddle.net>
Cc: Jan Kiszka <jan.kiszka@web.de>,
qemu-devel@nongnu.org, gdb@sourceware.org
Subject: Re: [PATCH] tcg: Use the GDB JIT debugging interface.
Date: Sun, 02 Oct 2011 02:04:00 -0000 [thread overview]
Message-ID: <CAN9gPaE3X2TD46GTDohHNLRTHxgX8SCDVbCk24bL_mdTiz4A7A@mail.gmail.com> (raw)
In-Reply-To: <4E85D3DF.7070307@twiddle.net>
On Fri, Sep 30, 2011 at 10:36 AM, Richard Henderson <rth@twiddle.net> wrote:
> On 09/30/2011 12:12 AM, Jan Kiszka wrote:
>>> Breakpoint 1, __ldb_mmu (addr=1001716, mmu_idx=0)
>>> at /home/rth/work/qemu/qemu/softmmu_template.h:86
>>> 86 {
>>> (gdb) where
>>> #0 __ldb_mmu (addr=1001716, mmu_idx=0)
>>> at /home/rth/work/qemu/qemu/softmmu_template.h:86
>>> #1 0x0000000040000afc in ?? ()
> ...
>> Would it be possible to tag translated code as well? At TB or maybe even
>> input instruction level? Only in debugging mode of course.
>
> I don't know. A couple of points on that:
>
> (1) I was rather expecting frame 1 above to be marked "code_gen_buffer"
> rather than "??". I *did* install that symbol in the generated
> ELF image as a function covering the entire buffer. So I'm not
> quite sure why GDB didn't use it.
Totally wild guess: associated with the wrong section? I don't
remember what we do w.r.t. ABS in shared libraries, but for non-ABS we
do validate what section we think things are in. And I'm not sure if
we load section info in the JIT loader, either.
--
Thanks,
Daniel
prev parent reply other threads:[~2011-10-02 2:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 23:47 Richard Henderson
2011-09-30 7:12 ` Jan Kiszka
2011-09-30 14:36 ` Richard Henderson
2011-10-02 2:04 ` Daniel Jacobowitz [this message]
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=CAN9gPaE3X2TD46GTDohHNLRTHxgX8SCDVbCk24bL_mdTiz4A7A@mail.gmail.com \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=jan.kiszka@web.de \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).