This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
java/1634: Unable to debug C++ app loaded by Java JNI
- From: mawatson at lehman dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 30 Apr 2004 14:02:22 -0000
- Subject: java/1634: Unable to debug C++ app loaded by Java JNI
- Reply-to: mawatson at lehman dot com
>Number: 1634
>Category: java
>Synopsis: Unable to debug C++ app loaded by Java JNI
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Apr 30 14:08:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: Mark Watson
>Release: 6.1 (Also present in 5.3 and 6.0)
>Organization:
>Environment:
Linux x86 - RedHat AS 2.1
>Description:
I am trying to debug a C++ app launched via Java JNI. i.e the whole app is launched via Java, which loads the app as a dynamic library.
gdb appears to be unable to debug the app, if it is started via gdb. I found it also reports the same error when debugging Java by itself (i.e. without our classes). Note that it appears to be possible to attach to the process successfully after start up.
The error reported is:
"[New Thread 8192 [LWP 18329)]
Cannot find user-level thread for LWP 18429: generic error "
The app versions used are:
gdb: 5.3, 6.0 and 6.1
glibc: libc-2.2.4.so -> with pthreads patches from RedHat (2.2.4-32.15). I have also tested with Debian unstable as of 29/4/04 - 2.3.2 iirc).
Please do not hesitate to contact me if you need more details or I can test anything.
>How-To-Repeat:
gdb java
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: