|
| From: | Mike Miller |
| Subject: | [Octave-bug-tracker] [bug #47568] Memory corruption in IO |
| Date: | Wed, 30 Mar 2016 15:27:58 +0000 |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 |
Update of bug #47568 (project octave):
Category: None => Octave Function
Severity: 3 - Normal => 4 - Important
Item Group: None => Crash
Status: None => Need Info
_______________________________________________________
Follow-up Comment #1:
Thanks for the bug report. This test works fine for me, so we need some more
information to help identify the bug if there is one.
Can you identify specifically which test causes the segfault and provide a gdb
backtrace? Something like the following:
$ ./run-octave -cli -g --path $srcdir/libinterp/corefcn \
--eval "more off; test file-io.cc verbose"
... startup messages ...
(gdb) r
... tests run ...
... test crashes presumably ...
(gdb) bt
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?47568>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |