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 tdep/29814] New: [gdb/tdep, powerpc64le] FAIL: gdb.base/msym-bp-shl.exp: debug=0: before run: info breakpoint
Date: Mon, 21 Nov 2022 13:27:43 +0000 [thread overview]
Message-ID: <bug-29814-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29814
Bug ID: 29814
Summary: [gdb/tdep, powerpc64le] FAIL:
gdb.base/msym-bp-shl.exp: debug=0: before run: info
breakpoint
Product: gdb
Version: 12.1
Status: NEW
Severity: normal
Priority: P2
Component: tdep
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With a gdb 12.1 based package on powerpc64le and target board unix/-fPIE/-pie,
I run into:
...
(gdb) PASS: gdb.base/msym-bp-shl.exp: debug=0: before run: break foo
info breakpoint^M
Num Type Disp Enb Address What^M
1 breakpoint keep y <MULTIPLE> ^M
1.1 y 0x00000000000008d4 <foo+12>^M
1.2 y 0x0000000000000a34
../sysdeps/powerpc/powerpc64/crti.S:88^M
(gdb) FAIL: gdb.base/msym-bp-shl.exp: debug=0: before run: info breakpoint
...
What seems to be happening it that foo@plt:
...
0000000000000a28 <foo@plt>:
a28: c0 ff ff 4b b 9e8 <__glink_PLTresolve>
Disassembly of section .fini:
0000000000000a2c <_fini>:
a2c: 02 00 4c 3c addis r2,r12,2
a30: d4 74 42 38 addi r2,r2,29908
a34: a6 02 08 7c mflr r0
...
is part of .text and (perhaps because of that) treated as a regular function,
so we add 8 to get past the global entry point, which gets us to 0xa30 in
_fini, and then (considering it part of prologue) skip past that insn to get to
0xa34.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-11-21 13:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 13:27 vries at gcc dot gnu.org [this message]
2022-11-21 16:32 ` [Bug tdep/29814] " vries at gcc dot gnu.org
2022-11-23 10:14 ` vries at gcc dot gnu.org
2022-11-23 11:11 ` vries at gcc dot gnu.org
2022-11-23 11:59 ` uweigand at gcc dot gnu.org
2022-11-23 16:16 ` vries at gcc dot gnu.org
2022-11-23 16:37 ` cel at us dot ibm.com
2022-11-23 17:03 ` uweigand at gcc dot gnu.org
2022-11-23 20:43 ` cel at us dot ibm.com
2022-11-24 12:45 ` vries at gcc dot gnu.org
2022-11-28 9:50 ` cvs-commit at gcc dot gnu.org
2022-11-28 9:51 ` 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-29814-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: link
Be 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).