From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7475 invoked by alias); 23 Feb 2005 17:25:56 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 7341 invoked from network); 23 Feb 2005 17:25:51 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 23 Feb 2005 17:25:51 -0000 Received: from drow by nevyn.them.org with local (Exim 4.44 #1 (Debian)) id 1D40Gg-0002cH-Ga; Wed, 23 Feb 2005 12:25:46 -0500 Date: Wed, 23 Feb 2005 18:37:00 -0000 From: Daniel Jacobowitz To: John Que Cc: gdb@sources.redhat.com Subject: Re: debugging a core dump generated from Java with JNI Message-ID: <20050223172545.GA8599@nevyn.them.org> Mail-Followup-To: John Que , gdb@sources.redhat.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6+20040907i X-SW-Source: 2005-02/txt/msg00151.txt.bz2 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