Re: gdb breaking down at printing variable

["André Pönitz" <andre.poenitz@nokia.com>]

On Thursday 26 August 2010 22:54:58 ext Tom Tromey wrote:
> >>>>> "André" == André Pönitz <andre.poenitz@nokia.com> writes:
> 
> André> This is most likely http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44731 
> André> i.e. not gdb's fault.
> 
> I think there actually is a gdb bug here.  gdb should be resilient even
> when the inferior's memory is trashed.

In my response I also said

  >> [...] I am pretty sure it can be triggered independently by uninitialized 
  >> or corrupted data in the "real" vector object containing the same "noise".

I do acknowledge that there are two independent issues, one gcc and 
one gdb related. I mostly meant to say that even if gdb were not at fault
Vikas Mishra's problem would still exist due to the gcc bug (and I was
assuming that the problems of uninitialized data and gdb's own pretty-
printers had been discussed often enough in the past to not reiterate ;-)).

Andre'