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: Thu, 26 Aug 2010 14:54:58 -0600
Subject: Re: gdb breaking down at printing variable
References: <AANLkTikOMH8JmwpDMNj2M2-4eK5Pq3+Vc8BGk0Pxk84y@mail.gmail.com> <201008261425.21062.andre.poenitz@nokia.com>

>>>>> "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.

There is a known problem that lazy_string is not fully lazy: it is read
eagerly before printing.  So if you make a very large lazy string, gdb
will internal error.

This wasn't in bugzilla, so I filed:

    http://sourceware.org/bugzilla/show_bug.cgi?id=11948

Tom

Follow-Ups:
- Re: gdb breaking down at printing variable
  - From: AndrÃ PÃnitz

References:
- gdb breaking down at printing variable
  - From: Vikas Mishra
- 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]