Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb@sourceware.org
Subject: Re: GDB and the OpenJDK JVM
Date: Thu, 09 Feb 2012 20:47:00 -0000	[thread overview]
Message-ID: <CAN9gPaHkq_mnOhUUyeSY1e5ZDOMMQNCLb0S8x01Csf40mEu3cg@mail.gmail.com> (raw)
In-Reply-To: <1328818882.2213.9.camel@soleil>

On Thu, Feb 9, 2012 at 3:21 PM, Philippe Waroquiers
<philippe.waroquiers@skynet.be> wrote:
> On google, the keywords 'java debugger interface' points at some
> "standardised" documents (including a "wire protocol") aiming at
> connecting a debugger to a JVM.

That's something completely different - how to talk to the JVM for
bytecode or source level debugging of the code running on the VM.  I'm
talking about debugging the underlying JVM in order to debug native
code such as JNI.

Now, it might be possible to simultaneously control the VM using
ptrace and let enough of it free-run to speak JDWP to it.  It would be
a bit of a trick, though... I wouldn't even raise the idea if non-stop
weren't so far along.

-- 
Thanks,
Daniel


  reply	other threads:[~2012-02-09 20:47 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 [this message]
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=CAN9gPaHkq_mnOhUUyeSY1e5ZDOMMQNCLb0S8x01Csf40mEu3cg@mail.gmail.com \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=philippe.waroquiers@skynet.be \
    /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