[Octave-bug-tracker] [bug #59599] movmean crashes Octave

[Markus Mützel]

Follow-up Comment #3, bug #59599 (project octave):

It might be or might not be an over-committing issue.
IIUC what is described in [1], Windows will over-commit memory on the stack
(but not on the heap?).
Maybe something has changed in how we allocate memory between versions...

Could you please check if you can catch the error with "gdb"?
For this, you could run "__debug_octave__" at the Octave prompt and continue
Octave's execution with "c" at the "(gdb)" prompt.
Back in Octave, try to execute the commands that lead to the crash.
When it happens, return to the gdb prompt and try to get the backtrace with
"bt".
What does that display?


[1]:
https://superuser.com/questions/1194263/will-microsoft-windows-10-overcommit-memory

    _______________________________________________________

Reply to this item at:

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

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