This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gdb breaking down at printing variable

From: Tom Tromey <tromey at redhat dot com>
To: AndrÃ PÃnitz <andre dot poenitz at nokia dot com>
Cc: gdb at sourceware dot org
Date: Fri, 27 Aug 2010 09:21:50 -0600
Subject: Re: gdb breaking down at printing variable
References: <AANLkTikOMH8JmwpDMNj2M2-4eK5Pq3+Vc8BGk0Pxk84y@mail.gmail.com> <201008261425.21062.andre.poenitz@nokia.com> <m3vd6xumal.fsf@fleche.redhat.com> <201008271140.58307.andre.poenitz@nokia.com>

>>>>> "AndrÃ" == AndrÃ PÃnitz <andre.poenitz@nokia.com> writes:

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

Yeah, sorry I misunderstood.

Tom

References:
- gdb breaking down at printing variable
  - From: Vikas Mishra
- Re: gdb breaking down at printing variable
  - From: André Pönitz
- Re: gdb breaking down at printing variable
  - From: Tom Tromey
- Re: gdb breaking down at printing variable
  - From: AndrÃ PÃnitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]