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

[Mike Miller]

Update of bug #53733 (project octave):

                Category:                    None => Libraries              
                  Status:                    None => Confirmed              

    _______________________________________________________

Follow-up Comment #3:

I can reproduce this crash with Octave 4.2.2 and Octave 4.3.91, both are
linked with OpenJDK 9, including the Debian package octave 4.2.2-2.

I have a self-compiled Octave 4.2.2 that is linked with OpenJDK 8. It does not
immediately appear to crash in the same way. But when I run it under gdb, it
does generate a segmentation fault.

The image package is not needed at all to reproduce this error. The imwrite
function is part of Octave, no packages or init files are needed.

In fact the call to 'imwrite' is not needed at all either. When it is not
present, octave appears to run and exit normally, but under gdb the
segmentation fault can still be seen. The minimal example


javaaddpath (".")
graph = javaObject ("Baz");


still generates a segmentation fault when run under gdb.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/