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/30695] New: [gdb, tsan] FAIL: gdb.base/bg-exec-sigint-bp-cond.exp: no force memory write: SIGINT does not interrupt background execution Date: Sat, 29 Jul 2023 07:18:34 +0000 [thread overview] Message-ID: <bug-30695-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30695 Bug ID: 30695 Summary: [gdb, tsan] FAIL: gdb.base/bg-exec-sigint-bp-cond.exp: no force memory write: SIGINT does not interrupt background execution Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- With an -fsanitize=thread build, I ran into: ... FAIL: gdb.base/bg-exec-sigint-bp-cond.exp: no force memory write: SIGINT does not interrupt background execution FAIL: gdb.base/bg-exec-sigint-bp-cond.exp: force memory write: SIGINT does not interrupt background execution ... The first in more detail: ... (gdb) PASS: gdb.base/bg-exec-sigint-bp-cond.exp: no force memory write: break foo if <condition> c&^M Continuing.^M (gdb) ^M Breakpoint 2, foo () at /labs/tdevries/gdb/src/gdb/testsuite/gdb.base/bg-exec-sigint-bp-cond.c:23^M 23 return 0;^M FAIL: gdb.base/bg-exec-sigint-bp-cond.exp: no force memory write: SIGINT does not interrupt background execution ... Instead, we expect to see: ... (gdb) PASS: gdb.base/bg-exec-sigint-bp-cond.exp: no force memory write: break foo if <condition> c&^M Continuing.^M (gdb) Quit^M (gdb) quit_count=1 Quit^M (gdb) quit_count=2 Quit^M (gdb) quit_count=3 Quit^M (gdb) quit_count=4 Quit^M (gdb) quit_count=5 Quit^M (gdb) quit_count=6 Quit^M (gdb) quit_count=7 Quit^M (gdb) quit_count=8 Quit^M (gdb) quit_count=9 Quit^M (gdb) quit_count=10 ^M Breakpoint 2, foo () at /data/vries/gdb/src/gdb/testsuite/gdb.base/bg-exec-sigint-bp-cond.c:23^M 23 return 0;^M PASS: gdb.base/bg-exec-sigint-bp-cond.exp: no force memory write: SIGINT does not interrupt background execution ... Triggering this may be a timing issue, this is on a fast server with lots of memory. On my laptop, the test passes with an -fsanitize=thread build. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-07-29 7:18 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-29 7:18 vries at gcc dot gnu.org [this message] 2023-07-29 7:29 ` [Bug gdb/30695] " vries at gcc dot gnu.org 2023-08-02 0:35 ` vries at gcc dot gnu.org 2023-08-02 14:38 ` 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-30695-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).