From: Tom Tromey <tom@tromey.com>
To: David Griffiths <dgriffiths@undo.io>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
Andrew Burgess <andrew.burgess@embecosm.com>,
dwk <dwks42@gmail.com>, GDB <gdb@sourceware.org>
Subject: Re: Is nexti confused by pushq?
Date: Tue, 26 Feb 2019 19:05:00 -0000 [thread overview]
Message-ID: <87h8cqfk0k.fsf@tromey.com> (raw)
In-Reply-To: <CA++j6c7=KNZgErDbEyEi81MUAVwYKeDC8dfPxGT_w=EBqUzNsA@mail.gmail.com> (David Griffiths's message of "Tue, 26 Feb 2019 11:50:37 +0000")
>>>>> "David" == David Griffiths <dgriffiths@undo.io> writes:
David> Ok, so in my case this is generated code with no debug info (Java JIT
David> generated) so does that mean I shouldn't attempt to use nexti? (I've got
David> other issues which probably preclude using nexti anyway but just curious)
There are a few options to deal with this sort of problem.
As Jan said, the JIT could generate debug info using one of the
gdb-provided JIT interfaces. That's kind of heavyweight but gives a lot
of control.
Another option is to write an unwinder in Python. The crucial thing
here is to ensure that the frame ID is constant for the duration of a
frame. In DWARF this is done by using the CFA as part of the identity;
for the JIT you'd want to do something similar. I thought there was
already such an unwinder for OpenJDK at least... ?
Tom
next prev parent reply other threads:[~2019-02-26 19:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA++j6c4bKPiWgYsSp2ajPLrJmv4wQ6Fb_Z=nXfs7TTOjzAqKRg@mail.gmail.com>
2019-02-25 15:54 ` dwk
2019-02-26 7:32 ` Andrew Burgess
2019-02-26 10:12 ` Jan Kratochvil
2019-02-26 11:50 ` David Griffiths
2019-02-26 11:58 ` Jan Kratochvil
2019-02-26 14:19 ` Dmitry Samersoff
2019-02-26 14:42 ` David Griffiths
2019-02-26 19:05 ` Tom Tromey [this message]
2019-02-27 7:59 ` Dmitry Samersoff
2019-02-27 14:53 ` Tom Tromey
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=87h8cqfk0k.fsf@tromey.com \
--to=tom@tromey.com \
--cc=andrew.burgess@embecosm.com \
--cc=dgriffiths@undo.io \
--cc=dwks42@gmail.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@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