From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Mark Wielaard <mjw@redhat.com>, gdb@sourceware.org
Subject: Re: GDB and the OpenJDK JVM
Date: Mon, 13 Feb 2012 19:39:00 -0000 [thread overview]
Message-ID: <CAN9gPaHqDp0uEuzagB_z5dooA2qNg2r7dB7XoJLpOWBZZ_QbFQ@mail.gmail.com> (raw)
In-Reply-To: <87ty2ulfyp.fsf@fleche.redhat.com>
On Mon, Feb 13, 2012 at 1:56 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
>
> Daniel> I'll do it if I have to, but I'd rather rely on the symbol table
> Daniel> of the JDK and manually maintained code.
>
> The new JIT API in gdb may be what you want. You can write a .so that
> ships with the JDK that knows about JDK internals, but that plugs into
> gdb. It doesn't expose everything, but I think would be sufficient for
> unwinding.
Neat! I was going to say "no, the JIT API is too limited" but I'm
glad I looked first :-) It looks like there's no NEWS entry for
Sanjoy's work, so I missed it the first time.
I wonder if this API could be implemented in Python...
--
Thanks,
Daniel
next prev parent reply other threads:[~2012-02-13 19:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 19:58 Daniel Jacobowitz
2012-02-09 16:16 ` Gary Benson
2012-02-09 18:33 ` Daniel Jacobowitz
2012-02-09 20:21 ` Philippe Waroquiers
2012-02-09 20:47 ` Daniel Jacobowitz
2012-02-09 21:15 ` Philippe Waroquiers
2012-02-13 18:39 ` Daniel Jacobowitz
2012-02-10 17:24 ` Gary Benson
2012-02-13 9:11 ` Mark Wielaard
2012-02-13 18:44 ` Daniel Jacobowitz
2012-02-13 18:57 ` Tom Tromey
2012-02-13 19:39 ` Daniel Jacobowitz [this message]
2012-02-13 19:54 ` 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=CAN9gPaHqDp0uEuzagB_z5dooA2qNg2r7dB7XoJLpOWBZZ_QbFQ@mail.gmail.com \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=mjw@redhat.com \
--cc=tromey@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