[Octave-bug-tracker] [bug #57632] 5.1.90 crash on cygwin

[marco atzeri]

Follow-up Comment #10, bug #57632 (project octave):

No failures again.
I am not aware on any problem specific problem in Cygwin relative to fseek,
and I never had such problem in any previous version including 5.1.

I run also one of the failing test under GDB but nothing useful
is coming out:

octave:1> f = tempname ()
f = /tmp/oct-1TDWkD
octave:2> fid = fopen (f, "w+")
fid =  3
octave:3> fprintf (fid, "1\n2\n3\n4\n5\n6")
octave:4> fclose [Thread 6232.0x29ac exited with code 0]
[Thread 6232.0x436c exited with code 0]
[Thread 6232.0x28a8 exited with code 0]

ans = 0
octave:5> fid = fopen (f, "r+")
fid =  3
octave:6> c = textscan (fid, "%f %f", 2)

Thread 1 "octave-cli-5.1.90" received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) trace
Tracepoint 1 at 0x0
(gdb) bt
#0  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) info frame
Stack level 0, frame at 0x0:
 rip = 0x0; saved rip = <not saved>
 Outermost frame: previous frame identical to this frame (corrupt stack?)
 Arglist at 0xffffb460, args:
 Locals at 0xffffb460, Previous frame's sp is 0x0
(gdb)


    _______________________________________________________

Reply to this item at:

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

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