[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 18:06:11 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

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

Sorry, bug in the code of comment #50, second line in main() should allocate
space for two options,

JavaVMOption* options = new JavaVMOption[2];

This does not change the rest of the observations, and the program still
produces a segfault under gdb. As said before, the code is mainly the example
from the JNI JVM-invocation documentation at



Reply to this item at:


  Message sent via Savannah

reply via email to

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