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 09:28:58 +0000 [thread overview] Message-ID: <bug-29426-4717-cAs5cz3AmX@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29426-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29426 Lancelot SIX <lsix at lancelotsix dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lsix at lancelotsix dot com --- Comment #1 from Lancelot SIX <lsix at lancelotsix dot com> --- I could not see those issues on ubuntu-20.04 (gcc-9.4.0) nor ubuntu-22.04 (gcc-11.2.0). I finally managed to reproduce it on opensuse/tumbleweed which uses gcc-12.1.1. Turns out that if I compile the testcase with HEAD gcc (13.0.0) on ubuntu, I can reproduce the issue: ``` $ $HOME/opt/gcc/bin/gcc --version gcc (GCC) 13.0.0 20220729 (experimental) Copyright © 2022 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. # make check-gdb \ TESTS="gdb.mi/mi-var-invalidate-shlib.exp gdb.mi/mi-var-invalidate.exp" \ RUNTESTFLAGS=CC_FOR_TARGET=$HOME/opt/gcc/bin/gcc [...] Running /home/lsix/dev/binutils-gdb/_build/gdb/testsuite/../../../gdb/testsuite/gdb.mi/mi-var-invalidate-shlib.exp ... FAIL: gdb.mi/mi-var-invalidate-shlib.exp: separate_debuginfo=0: in new process: global_var recreated (unexpected output) FAIL: gdb.mi/mi-var-invalidate-shlib.exp: separate_debuginfo=1: in new process: global_var recreated (unexpected output) Running /home/lsix/dev/binutils-gdb/_build/gdb/testsuite/../../../gdb/testsuite/gdb.mi/mi-var-invalidate.exp ... FAIL: gdb.mi/mi-var-invalidate.exp: linteger not anymore in scope due to binary changes (unexpected output) FAIL: gdb.mi/mi-var-invalidate.exp: no type for invalid variable linteger (1) (unexpected output) === gdb Summary === # of expected passes 56 # of unexpected failures 4 ``` I’ll investigate further to see what changed in the compiler’s output. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-29 9:28 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 ` lsix at lancelotsix dot com [this message] 2022-07-29 10:05 ` [Bug mi/29426] " 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 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-cAs5cz3AmX@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).