[Top][All Lists]

[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: Sun, 29 Apr 2018 17:57:03 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

Follow-up Comment #51, bug #53733 (project octave):

Submit bug report to OpenJDK ?

The Java issues that were cited here consider the Segfault at JVM creation
resolved since basically summer 2017, so the issues are closed. Notably 
observed the bug on a Xeon X5675 processor, where indeed the simple program
now executes flawlessly. Wouldn't it be worthwhile re-opening the bug or
submitting a new issue on the fact that the test program still fails under gdb
on certain processors (possibly for a different reason)? This seriously
hampers debugging of programs using jvm-functionnality, as here, and also
indicates that something is still rotten in the land of JNI. However it would
probably be better if someone more knowledgeable than me in Java/JNI-matters
and generally in programming reported the bug. :-)

[Never mind the question in my previous comment: I imagine that if it were
easy to link octave with a non-openjdk JVM you'd have tried that.]


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]