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/27396] New: setup_xfail leaks into next test-case Date: Thu, 11 Feb 2021 10:52:48 +0000 [thread overview] Message-ID: <bug-27396-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27396 Bug ID: 27396 Summary: setup_xfail leaks into next test-case Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- When running the testsuite with target board, unix/gdb:debug_flags=-gdwarf-5 I first run into: ... (gdb) PASS: gdb.cp/temargs.exp: test value of I in templ_m info addr I^M ERROR: GDB process no longer exists GDB process exited with wait status 16930 exp19 0 0 CHILDKILLED SIGABRT SIGABRT UNRESOLVED: gdb.cp/temargs.exp: test address of I in templ_m DUPLICATE: gdb.cp/temargs.exp: test address of I in templ_m ERROR: Couldn't send print P == &a_global to GDB. ERROR: can not find channel named "exp19" ... and then in the next test-case: ... (gdb) set multiple-symbols ask^M (gdb) XPASS: gdb.cp/templates.exp: set multiple-symbols ask (PRMS gcc/49546) ... It seems the setup_xfail executed in temargs.exp: ... if $have_older_template_gcc { setup_xfail "*-*-*" } else { setup_xfail gcc/49546 "*-*-*" } gdb_test "print F" { = \(void \(\*\)\(int\)\) 0x[0-9a-f]+ <S3::m\(int\)>} \ "test value of F in k3_m" ... is effective here in templates.exp: ... gdb_test_no_output "set multiple-symbols ask" ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-02-11 10:52 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-11 10:52 vries at gcc dot gnu.org [this message] 2021-02-11 11:06 ` [Bug testsuite/27396] " 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-27396-4717@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).