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/29196] New: [gdb, gcc-12/m32/pie] FAIL: gdb.base/gdb11531.exp: watchpoint variable triggers at next Date: Sat, 28 May 2022 07:55:55 +0000 [thread overview] Message-ID: <bug-29196-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29196 Bug ID: 29196 Summary: [gdb, gcc-12/m32/pie] FAIL: gdb.base/gdb11531.exp: watchpoint variable triggers at next 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: --- On openSUSE Tumbleweed with gcc-12, and with test-case gdb.base/gdb11531.exp and target board unix/-m32/-fPIE/-pie I run into: ... (gdb) PASS: gdb.base/gdb11531.exp: set watchpoint next^M 34 myrec.x = 5;^M (gdb) FAIL: gdb.base/gdb11531.exp: watchpoint variable triggers at next ... The problem is that normally runto main lands us at: ... Breakpoint 1, main () at /data/vries/gdb_versions/devel/src/gdb/testsuite/gdb.base/gdb11531.c:34^M 34 myrec.x = 5;^M (gdb) ... after which the next executes line 34. In this case however, runto main lands us at: ... Breakpoint 1, main () at /data/vries/gdb_versions/devel/src/gdb/testsuite/gdb.base/gdb11531.c:33^M 33 {^M (gdb) ... so the next executes line 33, and the watchpoint won't trigger. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-05-28 7:55 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-28 7:55 vries at gcc dot gnu.org [this message] 2022-05-28 8:04 ` [Bug gdb/29196] " vries at gcc dot gnu.org 2022-05-28 8:08 ` vries at gcc dot gnu.org 2022-05-28 8:26 ` vries at gcc dot gnu.org 2022-06-04 11:59 ` vries at gcc dot gnu.org 2022-06-08 9:17 ` vries at gcc dot gnu.org 2022-06-08 9:48 ` 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-29196-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).