This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: gdb.c++ testsuite 1.3: member_data_static.exp (resend)
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: Michael Elizabeth Chastain <mec at shout dot net>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Wed, 29 May 2002 03:00:04 -0700
- Subject: Re: gdb.c++ testsuite 1.3: member_data_static.exp (resend)
- Organization: Red Hat / Paris
- References: <200205282112.g4SLCap24212@duracef.shout.net>
- Reply-to: bkoz at redhat dot com
> As far as I can tell, gdb is reporting what's actually in the
> executable file. 'test3' has one static member and no non-static
> members. So perhaps gcc is broken, but I don't understand your view
> that gdb is broken. Can you explain more? What do you *want* gdb to
> print here?
Perhaps it is a gcc error, I don't know.
I'd like
mec> (gdb) print test3
mec> $2 = {static data = <optimized out>}
to be
(gdb) print test3
$2 =
{<gnu_obj_2> = {static test = true, static key1 = 5, static key2 = 77,
static value = oriental}, _vptr.gnu_obj_2 = 0x8092efc,
static value_derived = etruscian }
I have
Alternatively, I'd like to be able to use explicit qualifications, to
look at static data members, like so:
(gdb) print gnu_obj_2<long>::antiquities;
$3 = etruscian
Seem reasonable?
-benjamin