[Bug varobj/11868] Don't call pretty printers for local variables that are not yet constructed

["jens.elmenthaler at verigy dot com" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #2 from Jens Elmenthaler <jens.elmenthaler at verigy dot com> 2011-11-15 15:52:54 UTC ---
(In reply to comment #1)
> We changed how errors are propagated from printers to varobj,
> which should help this problem a bit -- you should get a more
> sensible display from properly written printers.
> Could you try this?
Yes, I just installed gdb 7.3.1 and will use it the next days.

> FWIW, I think trying to circumvent pretty-printing based on
> checking line numbers to see if initialization has occurred is
> likely to be fragile.  First, in the presence of optimization,
> this information is not really reliable.  Second, the same effect
> can be seen via data corruption anyway -- so it is better instead
> to try to come up with a solution that is robust in the presence
> of errors.
You are possibly right, relying on the line numbers will not really improve
robustness. I'm fine if you close this bug. There or other bugzillas to address
individual stability problems with one or the other command. In the case they
are missing, I will formulate them under the assumption that pretty printing
must never make gdb crash or hang, even if the pretty printer developer did a
mistake.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.