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 gdb/27742] FAIL: gdb.opt/inline-locals.exp: info locals above bar 2/3 Date: Fri, 16 Apr 2021 10:44:55 +0000 [thread overview] Message-ID: <bug-27742-4717-fnh25Pn4X9@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27742-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27742 Tom de Vries <vries at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot org --- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> --- Bisects to: ... commit 644a2e75ace6b5e76f91d38c28c3b97fcfdeeaa5 (HEAD) Author: Tom Tromey <tromey@adacore.com> Date: Thu Apr 15 10:14:11 2021 -0600 Use common_val_print_checked in print_variable_and_value ... Before: ... (gdb) PASS: gdb.opt/inline-locals.exp: func1 inlined 2 info locals^M array = {0 <repeats 64 times>}^M array = {<optimized out> <repeats 64 times>}^M (gdb) KFAIL: gdb.opt/inline-locals.exp: info locals above bar 2 (PRMS: gdb/25695) ... and after: ... (gdb) PASS: gdb.opt/inline-locals.exp: func1 inlined 2 info locals^M array = {0 <repeats 64 times>}^M array = <optimized out>^M (gdb) FAIL: gdb.opt/inline-locals.exp: info locals above bar 2 ... Should the KFAIL pattern be updated? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-16 10:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-16 9:16 [Bug gdb/27742] New: " vries at gcc dot gnu.org 2021-04-16 10:44 ` vries at gcc dot gnu.org [this message] 2021-04-16 16:40 ` [Bug gdb/27742] " tromey at sourceware dot org 2021-04-16 18:08 ` tromey at sourceware dot org 2021-04-16 18:12 ` vries at gcc dot gnu.org 2021-04-16 19:23 ` tromey at sourceware dot org 2021-04-19 13:16 ` cvs-commit at gcc dot gnu.org 2021-04-19 13:17 ` tromey at sourceware dot 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-27742-4717-fnh25Pn4X9@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).