Re: gdb namespaces/wrapper bug?

[Klaas Gadeyne <Klaas.Gadeyne@mech.kuleuven.ac.be>]

> Could you try CVS gdb?  I think the segfault has been fixed.  I may be
> mistaken about that, though.  This is related to
> lookup_transparent_type, which David has been doing some work on (and
> has more pending).

Hi Daniel,

Indeed, the infinite loop/segfault is gone with CVS gdb, however, the
behaviour is not yet as desired :)

====================================================================
[klaas@c014 /tmp]$ /usr/local/bin/gdb ./a.out
GNU gdb 2004-01-15-cvs
This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db
library "/lib/libthread_db.so.1".

(gdb) break wrapper.cpp:17
Breakpoint 1 at 0x80484f4: file wrapper.cpp, line 17.
(gdb) run
Starting program: /tmp/a.out

Breakpoint 1, main () at wrapper.cpp:17
17        Foo mywrapped;
(gdb) next
18        return 0;
(gdb) display mywrapped
1: mywrapped = {<> = {<No data fields>}, <No data fields>}
======================================================================

So mywrapped is now reported to be empty, where I expected to see
something like

1: mywrapped = {<Foo> = {<No data fields>}, <No data fields>}

regards,

klaas