From: Tom Tromey <tromey@redhat.com>
To: Kaushik Srenevasan <kaushik@twitter.com>
Cc: gdb@sourceware.org
Subject: Re: Hotspot JVM GDBJIT plugin
Date: Fri, 25 May 2012 14:37:00 -0000 [thread overview]
Message-ID: <87396o72f3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAN_uzpJ6PJHBpuJ_2JO8jwObvH+ck=TsngZ7riEX-KVU7R0tTg@mail.gmail.com> (Kaushik Srenevasan's message of "Thu, 24 May 2012 04:03:58 -0700")
>>>>> "Kaushik" == Kaushik Srenevasan <kaushik@twitter.com> writes:
Kaushik> I've been working on a Hotspot JVM JIT plugin for GDB
Very cool.
Kaushik> I'm writing to see if there is any interest in pulling the
Kaushik> changes [3] I've had to make to GDB, to get this to work.
Sure. Just send individual patches following the contribution
instructions...
Kaushik> The first of these changes [3] is a simple fix to a crash while
Kaushik> trying to display the return type of a JIT frame (say on
Kaushik> 'finish'.)
Sounds good.
Kaushik> The second (frame based symbol handler) is a feature added to
Kaushik> help GDB understand frames created by Hotspot's "template"
Kaushik> interpreter.
Kaushik> This adds an additional callback that the reader may choose to
Kaushik> implement to return the name (file path or line number) of the
Kaushik> function executing in the frame in question.
Phil has been working on a related feature in gdb, called "frame
filters". Frame filters let you write Python code to modify frames as
they are being displayed; you can change nearly any aspect of a frame,
and even insert and delete frames. The primary use case for this
feature is displaying better stack traces in interpreters.
So, you might consider just waiting for this and writing your frame
logic in Python.
If you'd rather press on, that is fine too.
Tom
next prev parent reply other threads:[~2012-05-25 14:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 11:04 Kaushik Srenevasan
2012-05-25 14:37 ` Tom Tromey [this message]
2012-05-25 19:50 ` Kaushik Srenevasan
2012-05-25 21:03 ` Tom Tromey
2012-05-30 18:13 ` Phil Muldoon
2012-05-31 21:05 ` Kaushik Srenevasan
2012-06-05 14:24 ` Daniel Jacobowitz
2012-06-05 22:21 ` Kaushik Srenevasan
2012-06-06 18:05 ` 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=87396o72f3.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=kaushik@twitter.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