public inbox for
help / color / mirror / Atom feed
From: "jens.elmenthaler at verigy dot com" <>
Subject: [Bug varobj/11868] Don't call pretty printers for local variables that are not yet constructed
Date: Tue, 15 Nov 2011 15:55:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

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

  parent reply	other threads:[~2011-11-15 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2011-11-10 21:48 ` tromey at redhat dot com
2011-11-15 15:55 ` jens.elmenthaler at verigy dot com [this message]
2012-06-02  6:54 ` xunxun1982 at gmail dot com
2012-06-02  7:08 ` asmwarrior at gmail dot com
2012-06-03 10:45 ` asmwarrior at gmail dot com
2023-08-31 16:34 ` tromey at sourceware dot org
2023-08-31 16:52 ` tromey at sourceware dot org
2023-08-31 17:19 ` tromey at sourceware dot org
2023-08-31 17:20 ` tromey at sourceware dot org
2010-08-02  7:40 [Bug varobj/11868] New: " jens dot elmenthaler at verigy dot com
2010-08-02 13:37 ` [Bug varobj/11868] " marc dot khouzam at ericsson dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).