Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Wielaard <mjw@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: GDB and the OpenJDK JVM
Date: Mon, 13 Feb 2012 18:44:00 -0000	[thread overview]
Message-ID: <CAN9gPaFjNYXrxi55zV7+xq_72qzk2wiO8i9LLMBdmt+SD5OMqA@mail.gmail.com> (raw)
In-Reply-To: <1329124283.2783.15.camel@springer.wildebeest.org>

On Mon, Feb 13, 2012 at 4:11 AM, Mark Wielaard <mjw@redhat.com> wrote:
> For SystemTap I wrote some hotspot heap introspection functions that
> might be interesting. But, like Gary said, hotspot might have internal
> debug accessor functions that you can use too. Systemtap cannot call
> into the inferior so we needed some code that went through the java code
> heap and stack unwind "by hand":
> http://icedtea.classpath.org/hg/icedtea6/file/tip/tapset/jstack.stp.in
> If you can make inferior function calls however (and know it is safe to
> call them) then that will be much easier. The above systemtap tapset is
> somewhat fragile since it depends on a lot of hotspot code generator
> internals.

Ooh, this is very interesting.  Thanks!

Overall, I would prefer not to call into the inferior.  That's how I
feel pretty much all the time, because (A) core dumps matter a great
deal, (B) calling the inferior is fragile in its own ways, and (C)
calling the inferior is slowwwwww.  I'll do it if I have to, but I'd
rather rely on the symbol table of the JDK and manually maintained
code.

-- 
Thanks,
Daniel


  reply	other threads:[~2012-02-13 18:44 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 [this message]
2012-02-13 18:57     ` Tom Tromey
2012-02-13 19:39       ` Daniel Jacobowitz
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=CAN9gPaFjNYXrxi55zV7+xq_72qzk2wiO8i9LLMBdmt+SD5OMqA@mail.gmail.com \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=mjw@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