From: Daniel Jacobowitz <drow@false.org>
To: Daniel Jacobowitz <drow@false.org>, gdb@sourceware.org
Subject: Re: GDB and the OpenJDK JVM
Date: Thu, 09 Feb 2012 18:33:00 -0000 [thread overview]
Message-ID: <CAN9gPaG-tb9Zv8GAO=htWqhg=LrQWxsv3qp82dJa=PhcQpJjAg@mail.gmail.com> (raw)
In-Reply-To: <20120209161612.GA7088@redhat.com>
On Thu, Feb 9, 2012 at 11:16 AM, Gary Benson <gbenson@redhat.com> wrote:
> Hi Daniel,
>
> Daniel Jacobowitz wrote:
>> Has anyone investigated non-trivial integration between GDB and this
>> (or any other) JVM? So far I haven't turned up anything useful. Some
>> examples of the sorts of integration I mean:
>>
>> * Showing information about Java objects given JNI handles
>> * Interleaving Java frames in the stack trace
>> * Fabricating unwind information for JIT'd code
>> * Automatically handling SEGVs related to the garbage collector
>> without hiding SEGVs for native code
>
> I don't know of anybody who has done any work in this area. I do know
> that HotSpot has a number of functions designed solely to be called by
> debuggers or debug code, and it's possible that #1 and #3 are covered
> that way. None of this stuff is documented anywhere I know of so it's
> worth asking on one of the HotSpot lists in case somebody can help.
Thanks! Is there a list you'd recommend?
--
Thanks,
Daniel
next prev parent reply other threads:[~2012-02-09 18:33 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 [this message]
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
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='CAN9gPaG-tb9Zv8GAO=htWqhg=LrQWxsv3qp82dJa=PhcQpJjAg@mail.gmail.com' \
--to=drow@false.org \
--cc=gdb@sourceware.org \
/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