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

[Adrian]

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

I can also confirm that the small test program crashes on an Intel i7-6600U.

In response to Rik's remark (comment #31), I upgraded gdb to 8.0 (the version
currently shipped in Debian-experimental) on both the Xeon and the Intel i5
system: the behaviour remains the same (no error on Xeon, segfault on i5).

@Dmitri A. Sergatskov: I'd be curious like Rik (comment #31) to know whether
you see the bug I reported, on your Xeon system where the small standalone
program runs fine. That is, if octave (in gdb or not) crashes (and when) if
given the commands


javaaddpath(".")
imwrite(zeros(1000), "foo.png");
graph = javaObject("Baz");
graph.addNodes(1:1000000);


As Rik commented, whatever the result does not really tell us if this is
related to the same bug or not, but it would give a better idea on the
reproductibility of this particular test. Up to here Mike Miller seems to have
observed the same bug (from the way I read his comment #3), but both Rik and
John W. Eaton see a segfault much earlier under gdb.


    _______________________________________________________

Reply to this item at:

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

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