[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: 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:01:52 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0

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

The same test code still causes a segfault in Octave for me.

With Octave 4.2.2 linked with Java 8, I get no segfault.

With Octave 4.2.2 linked with Java 9:

$ octave-cli --norc crashtest.m
panic: Segmentation fault -- stopping myself...
attempting to save variables to 'octave-workspace'...
warning: save: unable to save java objects, skipping
warning: called from
    crashtest at line 4 column 1
save to 'octave-workspace' complete
Segmentation fault

With Octave 4.3.92 linked with Java 9:

$ octave-cli --norc crashtest.m
fatal: caught signal Segmentation fault -- stopping myself...
Segmentation fault

If I reduce the size of the array passed in to addNodes, I get no segfault.

My processor is Intel(R) Core(TM) i7-4770HQ.


Reply to this item at:


  Message sent via Savannah

reply via email to

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