public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/31573] [gdb/testsuite] FAIL: gdb.base/ctf-ptype.exp: ptype linked list structure Date: Fri, 29 Mar 2024 09:00:32 +0000 [thread overview] Message-ID: <bug-31573-4717-uC3RjzyxCJ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31573-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31573 --- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> --- I build gdb at commit 9c2c346137e ("[gdb/testsuite] Use set always-read-ctf on instead of --strip-debug"), to see if there was a regression. At that commit, I only see the fails for gdb.ctf/funcreturn.exp. I tried to use readnow to see if that would fix those, but instead I got fails in gdb.ctf/multi.exp and gdb.ctf/cross-tu-cyclic.exp. I investigated why -readnow doesn't fix the gdb.ctf/funcreturn.exp fails, and found that the failure looks like this: ... (gdb) print v_char_func^M expression parsing not implemented for language "Auto"^M (gdb) FAIL: gdb.ctf/funcreturn.exp: print char function ... due to: ... $ gdb -q -batch -ex "set always-read-ctf on" -ex "file outputs/gdb.ctf/funcreturn/funcreturn" -ex "show lang" The current source language is "auto; currently c". ... vs: ... $ gdb -readnow -q -batch -ex "set always-read-ctf on" -ex "file outputs/gdb.ctf/funcreturn/funcreturn" -ex "show lang" The current source language is "auto; currently auto". ... Hm, language auto/auto. Haven't seen that one before. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-29 9:00 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-29 7:00 [Bug testsuite/31573] New: " vries at gcc dot gnu.org 2024-03-29 7:24 ` [Bug testsuite/31573] " vries at gcc dot gnu.org 2024-03-29 8:21 ` vries at gcc dot gnu.org 2024-03-29 8:31 ` vries at gcc dot gnu.org 2024-03-29 9:00 ` vries at gcc dot gnu.org [this message] 2024-03-29 11:52 ` vries at gcc dot gnu.org 2024-03-29 15:34 ` vries at gcc dot gnu.org 2024-03-30 8:41 ` vries at gcc dot gnu.org 2024-03-30 12:16 ` vries at gcc dot gnu.org
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-31573-4717-uC3RjzyxCJ@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).