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/31232] New: [gdb/testsuite, ppc64le] FAIL: gdb.dwarf2/dw2-entry-points.exp: bt foo Date: Thu, 11 Jan 2024 11:04:33 +0000 [thread overview] Message-ID: <bug-31232-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31232 Bug ID: 31232 Summary: [gdb/testsuite, ppc64le] FAIL: gdb.dwarf2/dw2-entry-points.exp: bt foo 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: --- On powerpc64le-linux, power10, with trunk I run into: ... Running /home/vries/gdb/src/gdb/testsuite/gdb.dwarf2/dw2-entry-points.exp ... FAIL: gdb.dwarf2/dw2-entry-points.exp: bt foo FAIL: gdb.dwarf2/dw2-entry-points.exp: continue to breakpoint: foobar (the program exited) FAIL: gdb.dwarf2/dw2-entry-points.exp: bt foobar FAIL: gdb.dwarf2/dw2-entry-points.exp: bt fooso ... First in more detail: ... (gdb) PASS: gdb.dwarf2/dw2-entry-points.exp: continue to breakpoint: foo bt^M #0 0x00000000100006dc in foobar (J=2)^M #1 0x000000001000070c in prog ()^M (gdb) FAIL: gdb.dwarf2/dw2-entry-points.exp: bt foo ... In contrast, with x86_64-linux I get: ... (gdb) PASS: gdb.dwarf2/dw2-entry-points.exp: continue to breakpoint: foo bt^M #0 0x00000000004004d9 in foo (J=1, K=0)^M #1 0x0000000000400503 in prog ()^M (gdb) PASS: gdb.dwarf2/dw2-entry-points.exp: bt foo ... The problem seems to be that foo and foobar end up at the same address: ... (gdb) break foo^M Breakpoint 2 at 0x100006dc^M (gdb) break foobar^M Note: breakpoint 2 also set at pc 0x100006dc.^M Breakpoint 3 at 0x100006dc^M ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-01-11 11:04 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-11 11:04 vries at gcc dot gnu.org [this message] 2024-01-11 11:43 ` [Bug testsuite/31232] " vries at gcc dot gnu.org 2024-01-11 12:56 ` vries at gcc dot gnu.org 2024-01-11 15:04 ` cvs-commit at gcc dot gnu.org 2024-01-11 15:05 ` 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-31232-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).