[Pkg-octave-devel] Bug#490588: octave-ftp: octave segfaults on clear all command

[Rafael Laboissiere]

* Rafael Laboissiere <rafael at debian.org> [2008-07-13 09:15]:

> It is curious that ftpobj appears twice, both as a dynamically linked
> function and as a user variable.  By the way, the following commands also
> cause a segmentation fault:
> 
> octave:1> clear ftpobj; clear ftpobj; whos

Some further information on this bug: I ran the above through gdb (with the
octave3.0-dbg pacakge installed) and got the following:

(sid) $ gdb -q octave
(no debugging symbols found)
(gdb) run -q
Starting program: /usr/bin/octave -q
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b4a792d4700 (LWP 7664)]
octave:1> clear ftpobj ; clear ftpobj ; whos

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x2b4a792d4700 (LWP 7664)]
0x00002b4a73c1afea in symbol_table::parse_whos_line_format (this=<value
optimized out>, symbols=@0x7fff3747a200) at ov.h:785
785       std::string type_name (void) const { return rep->type_name (); }
Current language:  auto; currently c++

 
-- 
Rafael