gdb breaking down at printing variable

Tom Tromey
Thu Aug 26 20:55:00 GMT 2010

>>>>> "André" == André Pönitz <> writes:

André> This is most likely 
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:


More information about the Gdb mailing list