This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [C++] static data members, gdb problems with
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Subject: Re: [C++] static data members, gdb problems with
- From: Daniel Berlin <dberlin at redhat dot com>
- Date: Wed, 30 Aug 2000 23:18:49 -0700 (PDT)
- cc: Benjamin Kosnik <bkoz at redhat dot com>, gcc at gcc dot gnu dot org, bug-gdb at gnu dot org
On Thu, 31 Aug 2000, Andrew Cagney wrote:
>
> Just BTW, if the debug info is corrupt then GDB should report an error()
> and not an internal_error(). Internal errors are more for when gdb's
> internal data structures turn out to be broken (and about to core dump
> :-).
>
> enjoy,
> Andrew
I'll bet then that this error should be an error, rather than
internal_error.
The only place i really see constant static variables used like that is in
libio,
so it's quite possible nobody noticed it before, or it affects such a
small population of users that nobody ever bothered to report it.
The part i love is where you do:
(gdb) p __ios_flags::_S_boolalpha
Internal error: could not find static variable _S_boolalpha
(gdb) p '__ios_flags::_S_boolalpha'
No symbol "__ios_flags::_S_boolalpha" in current context.
Dunno which is better, probably neither.
Either the user things something has gone horribly wrong, or thinks were
stupid.
--Dan