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

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

imwrite(zeros(1000), "foo.png");
graph = javaObject("Baz");

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:


  Message sent via Savannah

reply via email to

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