This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: debugging a core dump generated from Java with JNI
- From: Daniel Jacobowitz <drow at false dot org>
- To: John Que <qwejohn at hotmail dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Wed, 23 Feb 2005 12:25:46 -0500
- Subject: Re: debugging a core dump generated from Java with JNI
- References: <BAY14-F85467C4B93A07D4C1D727AF630@phx.gbl>
On Wed, Feb 23, 2005 at 06:55:15PM +0200, John Que wrote:
> Hello,
> I am developing a java application which calls a procedure in "C"
> using JNI.
>
> It is developed on a Linux RedHat 9 x86 intel box.
> Sometimes this procedure crashes and a coredeump (core.pid) file is created.
> So I wanted to know how to debug it; So i changed that "c" method so the
> only thing
> it does now is call abort() so it will make a core dump.
>
> I had build my c code with -g flag.
>
> When I opened gdb like thus:
>
> gdb /usr/java/usr/java/j2sdk1.4.2_06/bin/java core.pid
Sorry, but it looks like the JDK loads objects in a way that GDB
doesn't understand. You'd have to use a debugger that supported the
Sun JDK to debug this.
--
Daniel Jacobowitz
CodeSourcery, LLC