[Octave-bug-tracker] [bug #60620] [octave forge] (optim) 'expfit' function from optim-1.6.1 package terminates with segmentation fault

[anonymous]

Follow-up Comment #17, bug #60620 (project octave):

Yes, it is Java which is causing the segfault:

"
octave:1> version -java
OpenJDK 64-Bit Server VM warning: Archived non-system classes are disabled
because the java.system.class.loader property is specified (value =
"org.octave.OctClassLoader"). To use archived non-system classes, this
property must be not be set
ans = Java 11.0.11+9-Ubuntu-0ubuntu2.18.04 with Ubuntu OpenJDK 64-Bit Server
VM mixed mode, sharing
octave:2> load('-binary', 'foo.bin', 'foo')
octave:3> s = -foo.one\foo.two
Segmentation fault (core dumped)
".

I.e. if I first load Java and then try to perform the operation on saved data
('s = -foo.one\foo.two'), segfault occurs.

Without Java it doesn't occur.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60620>

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