Hello friends. I tracked down the problem and attached my results to
the relevant bug report. The issue is caused by using kernels after
the patches for CVE-2017-1000364. It can be worked around in a variety
of different ways until the problem is fixed in the kernel or JVM. You
can disable CVE-2017
I was bitten by this during jcc.initVM():
https://www.cloudlinux.com/cloudlinux-os-blog/entry/jvm-crashes-occurring-after-upgrading-to-a-kernel-with-the-fix-for-stack-clash
Maybe related...
--dirk
Am 06.07.2017, 23:50 Uhr, schrieb Joshua Campbell :
Okay so. I built GDB 8 from source (it's new
Okay so. I built GDB 8 from source (it's new) and that doesn't have bug.
In summary:
Ok TO BE CLEAR, I am closer to the TRUTH than ever. Not only am I not
stopping, I am working harder. Updates when available. Stay tuned!
It turns out the JVM is crashing on the line commented with "//
Generate S
How would they break oracle's though. It's a binary.
On Wed, Jul 5, 2017 at 10:40 PM, Andi Vajda wrote:
>
> > 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
> 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 for how to track it down
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
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,
>> **initvm_args)
>> ^ last python trace bef
> 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,
> **initvm_args)
> ^ last python trace before death
>
> Breakpoint 5, initVM (self=0x77e05048, args=0x766deac
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
> 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
(0x7f
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 on trunk and got the
> 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 jcc built with ?
> >
> 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 as
> 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 know how to debug thi
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 v
15 matches
Mail list logo