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: Mon, 30 Apr 2018 14:46:56 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

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

Well, that is interesting.  Of course, executing just imformats is enough to
load in the GraphicsMagick dldfcn, as well as execute some pretty intricate
code with persistent variables in subfunctions for which mlock has been
called.

It would help if the original reporter could verify the new proposed test code
still produces a segfault.


javaaddpath (".")
fmt = imformats ();
graph = javaObject ("Baz");
graph.addNodes (1:1e8);




    _______________________________________________________

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]