Comment 4 for bug 325118

Revision history for this message
In , Thomas (thomas-redhat-bugs) wrote :

Description of problem:
octave segfaults while executing "clear all".
It does not matter if any variables were defined.

Version-Release number of selected component (if applicable):
octave-3.0.1-1.fc9.x86_64
octave-forge-20080429-1.fc9.x86_64
atlas-3.6.0-15.fc9.x86_64

How reproducible:
always

Steps to Reproduce:
just execute octave --eval "clear all"

Actual results:
segmentation fault

Expected results:
no segmentation fault ;)

Additional info:
(gdb) run -q --eval "clear all"
Starting program: /usr/bin/octave -q --eval "clear all"
warning: "/usr/lib/debug/usr/lib64/atlas/liblapack.so.3.0.debug": The separate
debug info file has no debug info
warning: "/usr/lib/debug/usr/lib64/atlas/libblas.so.3.0.debug": The separate
debug info file has no debug info
[Thread debugging using libthread_db enabled]
[New Thread 0x7f8ddaa76700 (LWP 5636)]

Program received signal SIGSEGV, Segmentation fault.
0x00000032d95b8496 in symbol_record::clear (this=<value optimized out>) at ov.h:392
392 { return rep->is_defined (); }
Current language: auto; currently c++