* Rafael Laboissiere <[EMAIL PROTECTED]> [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>, [EMAIL PROTECTED]) at ov.h:785
785 std::string type_name (void) const { return rep->type_name (); }
Current language: auto; currently c++
--
Rafael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
