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: Mike Miller
Subject: [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write]
Date: Mon, 30 Apr 2018 14:22:25 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0

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

I don't know. But removing the call to imwrite makes a larger sized argument


javaaddpath (".")
graph = javaObject ("Baz");
graph.addNodes (1:100000000);


work just fine. It takes a while and is busy most of the time, doing
Octave-to-Java array type conversion I suspect, but exits without error.

Simply calling 'imformats' to print the image format types supported by
GraphicsMagick, instead of imwrite, is enough to allow the 1:1e6 argument to
lead to a segfault.

    _______________________________________________________

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]