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/31598] New: [gdb] FAIL: gdb.dwarf2/dw2-line-number-zero.exp: bar1, 1st next Date: Tue, 02 Apr 2024 20:35:10 +0000 [thread overview] Message-ID: <bug-31598-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31598 Bug ID: 31598 Summary: [gdb] FAIL: gdb.dwarf2/dw2-line-number-zero.exp: bar1, 1st 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 aarch64-linux (debian 12) I ran into: ... (gdb) PASS: gdb.dwarf2/dw2-line-number-zero.exp: continue to breakpoint: bar1 n^M ^M Breakpoint 2, bar1 () at /home/linux/gdb/src/gdb/testsuite/gdb.dwarf2/dw2-line-number-zero.c:27^M 27 foo (1);^M (gdb) FAIL: gdb.dwarf2/dw2-line-number-zero.exp: bar1, 1st next n^M 29 foo (2);^M (gdb) FAIL: gdb.dwarf2/dw2-line-number-zero.exp: bar1, 2nd next ... Not easily reproducible. I did manage to reproduce it once more, but didn't find a way to reliably reproduce it in say 100 or 500 runs. -- You are receiving this mail because: You are on the CC list for the bug.
reply other threads:[~2024-04-02 20:35 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-31598-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).