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

[anonymous]

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

[comment #19 comment #19:]
> Ok, I can also reproduce this in current versions of Octave, both version
6.2.0 and the version 7 development branch, if and only if running as
'octave-cli' (or equivalently with '--no-gui-libs').
> 
> It's also possible to reproduce this in any of these versions of Octave
without the optim package, so this can be separated from the expfit function
specifically.
> 
> I also get an error message printed directly by the Java runtime to the
console on my main Debian development system:
> 
> 
> >> A = rand (512, 512);
> >> x = rand (512, 1);
> >> y = A \ x;
> >> version -java
> ans = Java 11.0.11-ea+4-post-Debian-1 with Debian OpenJDK 64-Bit Server VM
mixed mode, sharing
> >> y = A \ x;
> An irrecoverable stack overflow has occurred.
> Please check if any of your loaded .so files has enabled executable stack
(see man page execstack(8))
> fatal: caught signal Segmentation fault -- stopping myself...
> Segmentation fault (core dumped)
> 

I think this discovery justifies changing the bug status to confirmed.

    _______________________________________________________

Reply to this item at:

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

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