From: Carl Love <cel@us.ibm.com>
To: gdb-patches@sourceware.org
Cc: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
Will Schmidt <will_schmidt@vnet.ibm.com>,
cel@us.ibm.com
Subject: [PATCH] PowerPC, add support for recording pipe2 system call.
Date: Thu, 20 Oct 2022 16:58:37 -0700 [thread overview]
Message-ID: <ddb5f38d6a68d5ede3fbef44d8cd5bc4c1125269.camel@us.ibm.com> (raw)
GCC maintainers:
The pipe2 system call support for gdb record is missing. The missing
support results in gdb.reverse/pipe-reverse.exp a single test failure.
This patch adds the needed support for the pipe2 system call on Power
10 with the Fedora 36 distro.
The patch has been tested on Power 10 with no regression failures.
Please let me know if this patch is acceptable for mainline. Thanks.
Carl Love
---------------------------
PowerPC, add support for recording pipe2 system call.
Test gdb.reverse/pipe-reverse.exp fails on Power 10 running the fedora 36
distro. The gdb record error message is:
Process record and replay target doesn't support syscall number 317.
System call 317 on PowerPC maps to the pipe2 system call.
This patch adds support for the missing pipe2 system call for PowerPC.
Patch fixes the test failure in gdb.reverse/pipe-reverse.exp.
The patch has been tested on Power 10 with no regression failures.
---
gdb/ppc-linux-tdep.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gdb/ppc-linux-tdep.c b/gdb/ppc-linux-tdep.c
index 14800619cbe..cc5a26431ba 100644
--- a/gdb/ppc-linux-tdep.c
+++ b/gdb/ppc-linux-tdep.c
@@ -1400,6 +1400,8 @@ ppc_canonicalize_syscall (int syscall, int wordsize)
else
result = gdb_sys_fstatat64;
}
+ else if (syscall == 317)
+ result = gdb_sys_pipe2;
else if (syscall == 336)
result = gdb_sys_recv;
else if (syscall == 337)
--
2.37.2
next reply other threads:[~2022-10-20 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 23:58 Carl Love [this message]
2022-10-21 15:20 ` Tom Tromey
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=ddb5f38d6a68d5ede3fbef44d8cd5bc4c1125269.camel@us.ibm.com \
--to=cel@us.ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=will_schmidt@vnet.ibm.com \
/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).