[Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write]

[Adrian]

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

@Mike Miller: I'd be curious to know whether the Octave 4.2.2 linked with
OpenJDK 8 that you mentioned in comment #3 still produces a segfault in gdb
once the SIGSEGV generated by the JVM for stack overflow detection have been
made non-fatal in gdb ("handle SIGSEGV nostop print pass" in .gdbinit).

Here's again the modification of the test from comment #59 that probes various
argument sizes:


javaaddpath (".")
fmt = imformats ();
graph = javaObject ("Baz");
for k=1:10
  N=10^k
  graph.addNodes (1:N);
endfor



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53733>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/