[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java metho
From: |
Adrian |
Subject: |
[Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write] |
Date: |
Fri, 27 Apr 2018 06:49:56 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 |
Follow-up Comment #28, bug #53733 (project octave):
Just as Dmitri in comment #20, the standalone JNI createJavaVM test program
from comment #12 runs fine for me, in gdb or not, while on the same machine
the original bug creates a segfault under gdb at the graph.addNodes
instruction.
The standalone program works both with openjdk-8 and openjdk-9 (minor
difference: error during plugin loading in gdb for openjdk-8, see below).
Here are the details on the test conditions:
GNU/Linux kernel 4.15.0-3-amd64 (Debian 4.15.17-1 (2018-04-19))
libc 2.27
GNU gdb (Debian 7.12-6+b1) 7.12.0.20161007-git
(side-note: the openjdk-8 test runs fine - with the same gdb.error for the
plugin - also on a fresh Debian stable install with kernel 4.9; openjdk-9 is
not packaged for stable yet)
openjdk-8:
$> g++ -ggdb3 -I/usr/lib/jvm/java-8-openjdk-amd64/include
-I/usr/lib/jvm/java-8-openjdk-amd64/include/linux jni_createVM_test.c
-L/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/server -ljvm -o
jni_createVM_test_openjdk-8
$> LD_LIBRARY_PATH=/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/server gdb
./jni_createVM_test_openjdk-8
GNU gdb (Debian 7.12-6+b1) 7.12.0.20161007-git
[snip]
(gdb) run
Starting program: /home/adrian/tmp/crashtest/jni_createVM_test_openjdk-8
Installing openjdk unwinder
Traceback (most recent call last):
File
"/usr/share/gdb/auto-load/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/server/libjvm.so-gdb.py",
line 52, in <module>
class Types(object):
File
"/usr/share/gdb/auto-load/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/server/libjvm.so-gdb.py",
line 66, in Types
nmethodp_t = gdb.lookup_type('nmethod').pointer()
gdb.error: No type named nmethod.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff7fc6700 (LWP 6565)]
[snip]
[New Thread 0x7fffcf3f3700 (LWP 6595)]
VM = 0x7ffff7d8ef20
[Thread 0x7fffcf3f3700 (LWP 6595) exited]
[snip]
[Thread 0x7ffff7fc7740 (LWP 6561) exited]
[Inferior 1 (process 6561) exited normally]
(gdb) quit
$>LD_LIBRARY_PATH=/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/server
./jni_createVM_test_openjdk-8
VM = 0x7f3687891f20
$>
openjdk-9:
$> g++ -ggdb3 -I/usr/lib/jvm/java-9-openjdk-amd64/include
-I/usr/lib/jvm/java-9-openjdk-amd64/include/linux jni_createVM_test.c
-L/usr/lib/jvm/java-9-openjdk-amd64/lib/server -ljvm -o
jni_createVM_test_openjdk-9
$> LD_LIBRARY_PATH=/usr/lib/jvm/java-9-openjdk-amd64/lib/server gdb
./jni_createVM_test_openjdk-9
GNU gdb (Debian 7.12-6+b1) 7.12.0.20161007-git
[snip]
Reading symbols from jni_createVM_test_openjdk-9...done.
(gdb) run
Starting program: /home/adrian/tmp/crashtest/jni_createVM_test_openjdk-9
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdbf22700 (LWP 6644)]
[snip]
[New Thread 0x7fff560d5700 (LWP 6694)]
VM = 0x7ffff7d6ad40
[Thread 0x7fff560d5700 (LWP 6694) exited]
[snip]
[Thread 0x7ffff7fc7740 (LWP 6640) exited]
[Inferior 1 (process 6640) exited normally]
(gdb) quit
$> LD_LIBRARY_PATH=/usr/lib/jvm/java-9-openjdk-amd64/lib/server
./jni_createVM_test_openjdk-9
VM = 0x7f1921ba0d40
$>
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?53733>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], (continued)
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Rik, 2018/04/24
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Dmitri A. Sergatskov, 2018/04/24
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Rik, 2018/04/24
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Rik, 2018/04/24
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Dmitri A. Sergatskov, 2018/04/24
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Rik, 2018/04/24
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Rik, 2018/04/24
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], John W. Eaton, 2018/04/25
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Rik, 2018/04/25
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Dmitri A. Sergatskov, 2018/04/25
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write],
Adrian <=
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Adrian, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], John W. Eaton, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Rik, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], John W. Eaton, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Adrian, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Adrian, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Adrian, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], John W. Eaton, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Adrian, 2018/04/27
- [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write], Adrian, 2018/04/27