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/29025] New: [gdb/testsuite] FAIL: gdb.mi/mi-cmd-user-context.exp: frame {1,2,3} (unexpected output) Date: Mon, 04 Apr 2022 14:13:37 +0000 [thread overview] Message-ID: <bug-29025-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29025 Bug ID: 29025 Summary: [gdb/testsuite] FAIL: gdb.mi/mi-cmd-user-context.exp: frame {1,2,3} (unexpected output) 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: --- While running the gdb testsuite for gdb-12-branch on openSUSE Tumbleweed, I ran into: ... FAIL: gdb.mi/mi-cmd-user-context.exp: frame 1 (unexpected output) FAIL: gdb.mi/mi-cmd-user-context.exp: frame 2 (unexpected output) FAIL: gdb.mi/mi-cmd-user-context.exp: frame 3 (unexpected output) ... I tried to reproduce, and managed by running in parallel with "stress -c 5", 4 times in a run of 25. The first FAIL looks like this in more detail: ... PASS: gdb.mi/mi-cmd-user-context.exp: info thread 5 Expecting: ^(frame[^M ]+)?(.*#0 .*child_sub_function .*[^M ]+[(]gdb[)] ^M [ ]*) frame^M &"frame\n"^M ~"#0 0x00007ffff7d3049a in pthread_barrier_wait@GLIBC_2.2.5 () from /lib64/libc.so.6\n"\ ^M ^done^M (gdb) ^M FAIL: gdb.mi/mi-cmd-user-context.exp: frame 1 (unexpected output) ... Reading through the source code, the behaviour makes sense. A breakpoint is set in main, after the call to pthread_barrier_wait. This guarantees that when the breakpoint is hit, all threads have reached the barrier, and guarantees that the main thread has left the barrier, but not that the other threads have left the barrier. So at first glance this looks like a testsuite problem. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-04-04 14:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-04 14:13 vries at gcc dot gnu.org [this message] 2022-04-04 14:22 ` [Bug testsuite/29025] " vries at gcc dot gnu.org 2022-04-04 14:32 ` vries at gcc dot gnu.org 2022-04-05 8:07 ` vries at gcc dot gnu.org 2022-04-05 12:18 ` simark at simark dot ca
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-29025-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).