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

[Evangelos Rozos]

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

[comment #3 comment #3:]
> 
> 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?
> 
> 

(gdb) c
Continuing.
Reading symbols from C:\var\OCTAVE~2.0-W\mingw32\bin\octave-gui.exe...
(No debugging symbols found in C:\var\OCTAVE~2.0-W\mingw32\bin\octave-
(gdb) c
Continuing.
[Thread 7712.0x10e0 exited with code 0]
[Thread 7712.0x8e4 exited with code 0]
[Thread 7712.0x1970 exited with code 0]
[New Thread 7712.0x354]
[Thread 7712.0xce4 exited with code 0]

Then back to Octave and give:

std (movmean (rand(40000,1), 365*10))


It crashes and in gdb I get the following:

[Thread 7712.0x20e4 exited with code 0]
[Thread 7712.0x25ac exited with code 0]
[Thread 7712.0x10c8 exited with code 3]
[Thread 7712.0xd00 exited with code 3]
[Thread 7712.0x1124 exited with code 3]
[Thread 7712.0xed0 exited with code 3]
[Thread 7712.0x354 exited with code 3]
[Thread 7712.0x2018 exited with code 3]
[Thread 7712.0x1e30 exited with code 3]
[Thread 7712.0x770 exited with code 3]
[Inferior 1 (process 7712) exited with code 03]
(gdb) bt
No stack.


    _______________________________________________________

Reply to this item at:

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

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