octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java metho


From: Rik
Subject: [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write]
Date: Fri, 27 Apr 2018 16:58:16 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

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

I'm still not convinced that this isn't machine, kernel, and tool-dependent. 
Even if the stand-alone program works on your machine, and octave-4.2.2 does
not, that could be explained by the linker getting lucky with where it has put
pages in memory.

I notice that you are using gdb version 7.12-6, while Dmitri is running
8.1-11.

@Dmitri: You reported that the test program worked for you.  Can you run a
session of Octave under gdb and try the OP's test sequence


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




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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