From: Eli Zaretskii <eliz@gnu.org>
To: timurgol007 <timurgol007@gmail.com>
Cc: tom@tromey.com, gdb-patches@sourceware.org, tdevries@suse.de
Subject: Re: [PATCH] This commit adds support for catching syscalls on riscv
Date: Wed, 10 Sep 2025 14:21:40 +0300 [thread overview]
Message-ID: <86wm66bliz.fsf@gnu.org> (raw)
In-Reply-To: <20250910093804.16250-1-timurgol007@gmail.com> (message from timurgol007 on Wed, 10 Sep 2025 12:38:04 +0300)
> From: timurgol007 <timurgol007@gmail.com>
> Cc: Timur Golubovich <timurgol007@gmail.com>
> Date: Wed, 10 Sep 2025 12:38:04 +0300
>
> From: Timur Golubovich <timurgol007@gmail.com>
>
> It affects following files:
> - gdb/riscv-linux-tdep.c: a function to get syscall number.
> - gdbserver/linux-riscv-low.cc: syscall trapinfo function to enable
> catching syscalls on remote targets.
> - gdb/syscalls/riscv-linux.xml.in: a file with syscalls, generated from
> linux kernel sources using gdb/syscalls/update-linux-from-src.sh script.
> - gdb/syscalls/riscv-linux.xml: a file with syscalls, patched with group
> names gdb/syscalls/apply-defaults.xsl using xsltproc tool.
> - gdb/syscalls/update-linux.sh: set startyear to 2025 on riscv.
> - gdb/syscalls/update-linux-from-src.sh: riscv syscall table must be
> generated from kernel headers.
> - gdb/NEWS: catch-syscall feature is now available on riscv.
> - gdb/data-directory/Makefile.in: adding file with syscalls to Makefile.
>
> Hi!
> Can you please look at this patch? It has 2 big autogenerated files, so
> it looks a bit complicated. But in fact it is quiet simple, so I would
> prefer to merge it.
> ---
> gdb/NEWS | 2 +
> gdb/data-directory/Makefile.in | 1 +
> gdb/riscv-linux-tdep.c | 26 ++
> gdb/syscalls/riscv-linux.xml | 340 +++++++++++++++++++++++++
> gdb/syscalls/riscv-linux.xml.in | 344 ++++++++++++++++++++++++++
> gdb/syscalls/update-linux-from-src.sh | 5 +
> gdb/syscalls/update-linux.sh | 3 +
> gdbserver/linux-riscv-low.cc | 24 ++
> 8 files changed, 745 insertions(+)
> create mode 100644 gdb/syscalls/riscv-linux.xml
> create mode 100644 gdb/syscalls/riscv-linux.xml.in
Thanks, the NEWS part is okay.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2025-09-10 11:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 9:38 timurgol007
2025-09-10 11:21 ` Eli Zaretskii [this message]
2025-09-16 12:31 ` Timur Golubovich
2025-09-23 10:53 ` Timur Golubovich
2025-09-23 18:13 ` Tom Tromey
2025-09-23 20:37 ` Timur Golubovich
-- strict thread matches above, loose matches on Subject: below --
2025-08-28 22:42 timurgol007
2025-09-04 9:00 ` Timur Golubovich
2025-09-04 9:23 ` Eli Zaretskii
2025-09-04 9:29 ` Timur Golubovich
2025-09-04 10:01 ` Eli Zaretskii
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=86wm66bliz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
--cc=timurgol007@gmail.com \
--cc=tom@tromey.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