From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 3/3] [gdb/tdep] Use ptrace events to get current syscall
Date: Wed, 22 Nov 2023 10:10:20 +0100 [thread overview]
Message-ID: <20231122091020.8640-3-tdevries@suse.de> (raw)
In-Reply-To: <20231122091020.8640-1-tdevries@suse.de>
Add a powerpc implementation of gdbarch_extended_event_to_syscall, for the
moment only mapping PTRACE_EVENT_EXEC to execve.
Use gdbarch_extended_event_to_syscall in linux_handle_extended_wait to
update the cached syscall number.
---
gdb/linux-nat.c | 5 +++++
gdb/ppc-linux-tdep.c | 17 +++++++++++++++++
2 files changed, 22 insertions(+)
diff --git a/gdb/linux-nat.c b/gdb/linux-nat.c
index ab6eadd557d..cbc52cafec3 100644
--- a/gdb/linux-nat.c
+++ b/gdb/linux-nat.c
@@ -1971,6 +1971,11 @@ linux_handle_extended_wait (struct lwp_info *lp, int status)
you have to be using PTRACE_SEIZE to get that. */
lp->syscall_state = TARGET_WAITKIND_SYSCALL_ENTRY;
+ struct gdbarch *gdbarch = target_thread_architecture (lp->ptid);
+ int syscall_number = gdbarch_extended_event_to_syscall (gdbarch, event);
+ if (syscall_number != -1)
+ lp->syscall_number = syscall_number;
+
if (event == PTRACE_EVENT_FORK || event == PTRACE_EVENT_VFORK
|| event == PTRACE_EVENT_CLONE)
{
diff --git a/gdb/ppc-linux-tdep.c b/gdb/ppc-linux-tdep.c
index 24e1b455afd..dffe1489144 100644
--- a/gdb/ppc-linux-tdep.c
+++ b/gdb/ppc-linux-tdep.c
@@ -64,6 +64,7 @@
#include "elf-bfd.h"
#include "producer.h"
#include "target-float.h"
+#include "nat/linux-ptrace.h"
#include "features/rs6000/powerpc-32l.c"
#include "features/rs6000/powerpc-altivec32l.c"
@@ -1373,6 +1374,19 @@ ppc_linux_get_syscall_number (struct gdbarch *gdbarch,
static struct linux_record_tdep ppc_linux_record_tdep;
static struct linux_record_tdep ppc64_linux_record_tdep;
+static int
+ppc_linux_extended_event_to_syscall (struct gdbarch *gdbarch, int event)
+{
+ switch (event)
+ {
+ case PTRACE_EVENT_EXEC:
+ /* Execve syscall. */
+ return 11;
+ }
+
+ return -1;
+}
+
/* ppc_canonicalize_syscall maps from the native PowerPC Linux set of
syscall ids into a canonical set of syscall ids used by process
record. (See arch/powerpc/include/uapi/asm/unistd.h in kernel tree.)
@@ -2173,6 +2187,9 @@ ppc_linux_init_abi (struct gdbarch_info info,
/* Get the syscall number from the arch's register. */
set_gdbarch_get_syscall_number (gdbarch, ppc_linux_get_syscall_number);
+ set_gdbarch_extended_event_to_syscall (gdbarch,
+ ppc_linux_extended_event_to_syscall);
+
/* SystemTap functions. */
set_gdbarch_stap_integer_prefixes (gdbarch, stap_integer_prefixes);
set_gdbarch_stap_register_indirection_prefixes (gdbarch,
--
2.35.3
next prev parent reply other threads:[~2023-11-22 9:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 9:10 [PATCH 1/3] [gdb/tdep] Add syscall number cache Tom de Vries
2023-11-22 9:10 ` [PATCH 2/3] [gdb/tdep] Add gdbarch_extended_event_to_syscall Tom de Vries
2023-11-22 9:10 ` Tom de Vries [this message]
2023-11-22 16:16 ` [PATCH 1/3] [gdb/tdep] Add syscall number cache John Baldwin
2023-11-24 21:09 ` Simon Marchi
2023-11-24 22:19 ` Tom de Vries
2023-11-27 15:52 ` Simon Marchi
2023-11-27 20:25 ` Tom de Vries
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=20231122091020.8640-3-tdevries@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@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).