From: Kaushik Srenevasan <kaushik@twitter.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb@sourceware.org
Subject: Re: Hotspot JVM GDBJIT plugin
Date: Thu, 31 May 2012 21:05:00 -0000 [thread overview]
Message-ID: <CAN_uzpLPA3KyNMz4PhKAQki2GzEGiR8vib1JD6nV9a7ydhEmsQ@mail.gmail.com> (raw)
In-Reply-To: <4FC66342.5080709@redhat.com>
On Wed, May 30, 2012 at 11:13 AM, Phil Muldoon <pmuldoon@redhat.com> wrote:
>>
>> The Python feature is really just about massaging the display of frames
>> already found by gdb. At least in the first revision there won't be a
>> way to hook into the unwinding process. We haven't even really
>> discussed letting people write unwinders in Python; I guess it could be
>> done.
>>
>
> The field substitution stuff is all there, I am currently working on
> the "elide" API which allows you to merge frames. As for trunk, I
> intend to submit it for review at the end of next week if I can. Then
> it is a matter of the usual review process after that.
>
Tom, Phil,
Thanks for the update. While it does seem like there is overlap, I
believe it'd be easier to implement both unwinding and symbol
resolution for frames in the same plugin - which could be the reader
or a python script. So, I'll go ahead and submit the frame based
symbol handler code I have for review.
-Kaushik
next prev parent reply other threads:[~2012-05-31 21:05 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
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 [this message]
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=CAN_uzpLPA3KyNMz4PhKAQki2GzEGiR8vib1JD6nV9a7ydhEmsQ@mail.gmail.com \
--to=kaushik@twitter.com \
--cc=gdb@sourceware.org \
--cc=pmuldoon@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).