public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Kaushik Srenevasan <kaushik@twitter.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Hotspot JVM GDBJIT plugin
Date: Fri, 25 May 2012 19:50:00 -0000	[thread overview]
Message-ID: <CAN_uzp+RDwg17jRFNfRYmXXo3VtRSG4QUTGVfBoy4JYx3LVmCw@mail.gmail.com> (raw)
In-Reply-To: <87396o72f3.fsf@fleche.redhat.com>

On Fri, May 25, 2012 at 7:36 AM, Tom Tromey <tromey@redhat.com> wrote:
> Sure.  Just send individual patches following the contribution
> instructions...
>
Will do.

> 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.
>
This was exactly what I was looking for when I started and since Python scripts
couldn't do it at the time, I wrote a JIT reader. I have a few questions though:

With frame filters, would JIT readers still be necessary to unwind the
frame or is
that done from Python too?
If they're not, are JIT readers going to be supported going forward?
When is this expected to hit trunk?

   -Kaushik

  reply	other threads:[~2012-05-25 19:50 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 [this message]
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=CAN_uzp+RDwg17jRFNfRYmXXo3VtRSG4QUTGVfBoy4JYx3LVmCw@mail.gmail.com \
    --to=kaushik@twitter.com \
    --cc=gdb@sourceware.org \
    --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).