This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: GDB and the OpenJDK JVM

From: Tom Tromey <tromey at redhat dot com>
To: Daniel Jacobowitz <drow at false dot org>
Cc: Mark Wielaard <mjw at redhat dot com>, gdb at sourceware dot org
Date: Mon, 13 Feb 2012 11:56:46 -0700
Subject: Re: GDB and the OpenJDK JVM
References: <CAN9gPaHVeZ+OTN47Tfqfdy4uCdDjU0du68q+8ZnuMf+uJjDqbg@mail.gmail.com> <1329124283.2783.15.camel@springer.wildebeest.org> <CAN9gPaFjNYXrxi55zV7+xq_72qzk2wiO8i9LLMBdmt+SD5OMqA@mail.gmail.com>

>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:

Daniel> I'll do it if I have to, but I'd rather rely on the symbol table
Daniel> of the JDK and manually maintained code.

The new JIT API in gdb may be what you want.  You can write a .so that
ships with the JDK that knows about JDK internals, but that plugs into
gdb.  It doesn't expose everything, but I think would be sufficient for
unwinding.

Tom

Follow-Ups:
- Re: GDB and the OpenJDK JVM
  - From: Daniel Jacobowitz

References:
- GDB and the OpenJDK JVM
  - From: Daniel Jacobowitz
- Re: GDB and the OpenJDK JVM
  - From: Mark Wielaard
- Re: GDB and the OpenJDK JVM
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]