public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "lsix at lancelotsix dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug mi/29426] FAIL: gdb.mi/mi-var-invalidate.exp: linteger not anymore in scope due to binary changes (unexpected output) Date: Fri, 29 Jul 2022 15:08:08 +0000 [thread overview] Message-ID: <bug-29426-4717-4FuMnbERH4@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29426-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29426 --- Comment #8 from Lancelot SIX <lsix at lancelotsix dot com> --- Created attachment 14242 --> https://sourceware.org/bugzilla/attachment.cgi?id=14242&action=edit add_varobj_global_flag.patch This regression also shows an interesting problem. Currently, when we unload an objfile and find a varobj which is linked to a block from this objfile, we clear the valid_block pointer to avoid having a stall pointer. However by doing this, we loose the ability to distinguish a varobj tracking a global (no valid_block associated) to a varobj tracking a local (some valid_block associated). Later, when we reload a new program and try to recreate varobj for globals, we have false positive and also try to recreate some locals as well. The attached patch fixes this, but some differences remain whether I ubuntu’s stock GCC or custom built HEAD GCC. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-29 15:08 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-28 14:33 [Bug mi/29426] New: " vries at gcc dot gnu.org 2022-07-29 9:28 ` [Bug mi/29426] " lsix at lancelotsix dot com 2022-07-29 10:05 ` vries at gcc dot gnu.org 2022-07-29 10:31 ` vries at gcc dot gnu.org 2022-07-29 11:05 ` vries at gcc dot gnu.org 2022-07-29 12:28 ` vries at gcc dot gnu.org 2022-07-29 13:01 ` lsix at lancelotsix dot com 2022-07-29 13:46 ` vries at gcc dot gnu.org 2022-07-29 15:08 ` lsix at lancelotsix dot com [this message] 2022-07-29 16:25 ` vries at gcc dot gnu.org 2022-08-12 11:12 ` lsix at lancelotsix 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-29426-4717-4FuMnbERH4@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).