public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug varobj/11868] Don't call pretty printers for local variables that are not yet constructed Date: Thu, 31 Aug 2023 16:34:23 +0000 [thread overview] Message-ID: <bug-11868-4717-GKJ3qWeCNX@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-11868-4717@http.sourceware.org/bugzilla/> 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.
next prev parent reply other threads:[~2023-08-31 16:34 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-11868-4717@http.sourceware.org/bugzilla/> 2011-11-10 21:48 ` tromey at redhat dot com 2011-11-15 15:55 ` jens.elmenthaler at verigy dot com 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 [this message] 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: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-11868-4717-GKJ3qWeCNX@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe 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).