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/28623] Missing catching return of execve syscall of PowerPC
Date: Thu, 16 Nov 2023 10:42:35 +0000 [thread overview]
Message-ID: <bug-28623-4717-nHld6iiiF1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28623-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28623
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Using this demonstrator patch I can hit the syscall exit:
...
diff --git a/gdb/ppc-linux-tdep.c b/gdb/ppc-linux-tdep.c
index 0c676a8..a5cfb7d 100644
--- a/gdb/ppc-linux-tdep.c
+++ b/gdb/ppc-linux-tdep.c
@@ -1344,6 +1344,8 @@
ppc_gdbarch_tdep *tdep = gdbarch_tdep<ppc_gdbarch_tdep> (gdbarch);
enum bfd_endian byte_order = gdbarch_byte_order (gdbarch);
+ return 11;
+
/* Make sure we're in a 32- or 64-bit machine */
gdb_assert (tdep->wordsize == 4 || tdep->wordsize == 8);
...
which allows me to sample the registers:
...
(gdb) info registers
r0 0x0 0
r1 0x7fffffffee10 140737488350736
r2 0x0 0
r3 0x0 0
r4 0x0 0
r5 0x0 0
r6 0x0 0
r7 0x0 0
r8 0x0 0
r9 0x0 0
r10 0x0 0
r11 0x0 0
r12 0x7ffff7fb19e0 140737353816544
r13 0x0 0
r14 0x0 0
r15 0x0 0
r16 0x0 0
r17 0x0 0
r18 0x0 0
r19 0x0 0
r20 0x0 0
r21 0x0 0
r22 0x0 0
r23 0x0 0
r24 0x0 0
r25 0x0 0
r26 0x0 0
r27 0x0 0
r28 0x0 0
r29 0x0 0
r30 0x0 0
r31 0x0 0
pc 0x7ffff7fb19e0 0x7ffff7fb19e0 <_start>
msr 0xb00000000000d033 12682136550675370035
cr 0x0 0
lr 0x0 0x0
ctr 0x0 0
xer 0x0 0
fpscr 0x0 0
vscr 0x0 0
vrsave 0xffffffff -1
ppr 0xc000000000000 3377699720527872
dscr 0x10 16
tar 0x0 0
bescr <unavailable>
ebbhr <unavailable>
ebbrr <unavailable>
mmcr0 0x0 0
mmcr2 0x0 0
siar 0x0 0
sdar 0x0 0
sier 0x0 0
orig_r3 0x7ffffffff1c5 140737488351685
trap 0xc00 3072
...
Looks like the lr == 0 approach might work here as well.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-11-16 10:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 19:27 [Bug gdb/28623] New: " simark at simark dot ca
2023-11-16 10:30 ` [Bug gdb/28623] " vries at gcc dot gnu.org
2023-11-16 10:42 ` vries at gcc dot gnu.org [this message]
2023-11-16 11:48 ` vries at gcc dot gnu.org
2023-11-16 11:50 ` [Bug tdep/28623] " vries at gcc dot gnu.org
2023-11-16 11:51 ` vries at gcc dot gnu.org
2023-11-16 17:00 ` ulrich.weigand at de dot ibm.com
2023-11-17 12:37 ` vries at gcc dot gnu.org
2023-11-17 14:32 ` ulrich.weigand at de dot ibm.com
2023-11-17 20:57 ` simon.marchi at polymtl dot ca
2023-11-20 15:44 ` vries at gcc dot gnu.org
2023-11-20 15:49 ` vries at gcc dot gnu.org
2023-11-21 12:42 ` vries at gcc dot gnu.org
2023-11-23 14:53 ` sam at gentoo dot 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-28623-4717-nHld6iiiF1@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).