This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: c++/1417: crash when printing variables
- From: David Carlton <carlton at kealia dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 10 Oct 2003 18:18:00 -0000
- Subject: Re: c++/1417: crash when printing variables
- Reply-to: David Carlton <carlton at kealia dot com>
The following reply was made to PR c++/1417; it has been noted by GNATS.
From: David Carlton <carlton@kealia.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: GNATS Filer <gdb-gnats@sources.redhat.com>
Subject: Re: c++/1417: crash when printing variables
Date: Fri, 10 Oct 2003 11:15:15 -0700
On 10 Oct 2003 17:58:00 -0000, Daniel Jacobowitz <drow@mvista.com> said:
> No, I won't. It's a bit more complicated than I had hoped.
> Hopefully for GDB 6.1 we'll have made progress in handling this
> thoroughly. David Carlton was doing some work in this area.
I tried out the test case on my branch. With stock GCC, it loops;
with a GCC that's patched to generate namespace info, it prints out
<incomplete type>. (Which is interesting, given that the program in
question doesn't explicitly use namespaces, but that's a separate
issue.)
It's probably the case that, when looking up a nested type A::B, my
branch works well if B really is defined in A, but gets it wrong if B
is defined in a superclass of A. Hmm. We'll certainly want to look
at this once my branch hits mainline (or before, if I have the time).
(Side note to Daniel: for various deadline reasons, it's unlikely that
I'll have time to generate the nested types patch this month; it might
happen, but if not I'll make it a high priority at the beginning of
November.)
Thanks for the test case; it will be useful.