gdb breaking down at printing variable

[Tom Tromey]

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