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

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

[tromey at redhat dot com]

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

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2011-11-10
                 CC|                            |tromey at redhat dot com
     Ever Confirmed|0                           |1

--- Comment #1 from Tom Tromey <tromey at redhat dot com> 2011-11-10 21:47:54 UTC ---
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?

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.

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

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

[jens.elmenthaler at verigy dot com]

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.

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

[xunxun1982 at gmail dot com]

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

xunxun <xunxun1982 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xunxun1982 at gmail dot com

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

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

[asmwarrior at gmail dot com]

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

asmwarrior <asmwarrior at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |asmwarrior at gmail dot com

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

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

[asmwarrior at gmail dot com]

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

--- Comment #3 from asmwarrior <asmwarrior at gmail dot com> 2012-06-03 10:44:45 UTC ---
Hi, Jens, I have a word around to filter out the local variables by compare the
current line and the declaration line of the local variable.

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

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

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

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
Comparing lines doesn't really work with optimizations.
There's not really a good way to handle this problem.
We've left it up to the printers but perhaps throwing
a memory exception could propagate to gdb, and it could
do something smarter.  Though of course printers can
catch that and still behave badly.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |17joshuanewcomb at gmail dot com

--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
*** Bug 22487 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xhpohanka at gmail dot com

--- Comment #6 from Tom Tromey <tromey at sourceware dot org> ---
*** Bug 21208 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[tromey at sourceware dot org]

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

--- Comment #7 from Tom Tromey <tromey at sourceware dot org> ---
*** Bug 12555 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[marc dot khouzam at ericsson dot com]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marc dot khouzam at ericsson
                   |                            |dot com


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.