Re: JCC Segfault on Debian 9 (stretch)

> On Jul 6, 2017, at 00:03, Joshua Campbell wrote: > > I confirmed that it crashes on multiple Debian 9 machines but it > doesn't crash on Ubuntu 16.04. This behavior is consistent regardless > of the JDK used (I tried openjdk 8, oracle 8 and openjdk 9). I am at a > loss

Re: JCC Segfault on Debian 9 (stretch)

I confirmed that it crashes on multiple Debian 9 machines but it doesn't crash on Ubuntu 16.04. This behavior is consistent regardless of the JDK used (I tried openjdk 8, oracle 8 and openjdk 9). I am at a loss for how to track it down further due to the (apparent) GDB bug. On Wed, Jul 5, 2017 at

Re: JCC Segfault on Debian 9 (stretch)

No, it segfaults. On Wed, Jul 5, 2017 at 2:26 PM, Andi Vajda wrote: > >> On Jul 5, 2017, at 22:16, Joshua Campbell wrote: >> >> It's occuring after JCC calls JNI_CreateJavaVM >> >> cpp.py(529): env = initVM(os.pathsep.join(classpath) or None, >>

Re: JCC Segfault on Debian 9 (stretch)

It's occuring after JCC calls JNI_CreateJavaVM cpp.py(529): env = initVM(os.pathsep.join(classpath) or None, **initvm_args) ^ last python trace before death Breakpoint 5, initVM (self=0x77e05048, args=0x766deac8, kwds=0x77e00ec8) at jcc3/sources/jcc.cpp:527 527

Re: JCC Segfault on Debian 9 (stretch)

> But you should get a better stacktrace ? I got the exact same stacktrace. $ ldd venv3/lib/python3.5/site-packages/JCC-3.0-py3.5-linux-x86_64.egg/libjcc3.so linux-vdso.so.1 (0x7ffcf4eb8000) libjava.so => /usr/lib/jvm/java-1.8.0-openjdk-amd64/jre/lib/amd64/libjava.so

Re: JCC Segfault on Debian 9 (stretch)

On Jul 5, 2017, at 18:56, Joshua Campbell wrote: >> What version if java is this jcc built with ? >> To build jcc for debugging with gcc add --debug to the build command. You > should then have symbols visible to gdb. > > You mean with setup.py build --debug ? I tried that

Re: JCC Segfault on Debian 9 (stretch)

> What version if java is this jcc built with ? Oh it's openjdk-8-dbg_8u131-b11-2 But I got a same result (the stacktrace was slightly different but still undecoded) with Oracle's JDK. On Wed, Jul 5, 2017 at 10:56 AM, Joshua Campbell wrote: > > What version if java is this

Re: JCC Segfault on Debian 9 (stretch)

> What version if java is this jcc built with ? > To build jcc for debugging with gcc add --debug to the build command. You should then have symbols visible to gdb. You mean with setup.py build --debug ? I tried that on trunk and got the same result. > Is the version of java used here the same

Re: JCC Segfault on Debian 9 (stretch)

> On Jul 5, 2017, at 18:25, Joshua Campbell wrote: > > This segfault appears to occur within the JVM code on both oracle-java8-jdk > and > java-1.8.0-openjdk-amd64. I installed the JVM debugging symbols but it > didn't seem to help. > > Occurs under python 2 and 3. I don't

JCC Segfault on Debian 9 (stretch)

This segfault appears to occur within the JVM code on both oracle-java8-jdk and java-1.8.0-openjdk-amd64. I installed the JVM debugging symbols but it didn't seem to help. Occurs under python 2 and 3. I don't know how to debug this any further. 0 joshua@buttercup unnaturalcode 17609$ python3 -m