From: Tom de Vries <tdevries@suse.de>
To: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Autogenerate gdb/syscalls/linux-defaults.xml.in (syscall groups) from strace sources
Date: Sat, 25 Feb 2023 10:31:55 +0100 [thread overview]
Message-ID: <ed367bac-a7ea-b5ca-e1cc-39b249123726@suse.de> (raw)
In-Reply-To: <20230224232650.4031472-1-pedro@palves.net>
On 2/25/23 00:26, Pedro Alves wrote:
> While working on the step-over-thread-clone/exit series, I noticed
> that one of the new tests was failing. The test does "catch syscall
> clone", and expects that pthread_create calls clone. Turns out that
> on the glibc shipped with Ubuntu 22.04, pthread_create calls clone3,
> not clone. To make the test cope with that, I thought of switching it
> to "catch syscall group:process". Surprisingly, that catches "clone",
> but not "clone3".
>
> This series fixes that, by adding a script that extracts the syscall
> group info out the strace sources.
>
If I understand correctly, this is orthogonal to update-linux-from-src.sh ?
[ FWIW, i've just ran update-linux-from-src.sh with linux kernel sources
v6.2, and there where no changes. ]
Thanks,
- Tom
> Pedro Alves (2):
> Autogenerate gdb/syscalls/linux-defaults.xml.in (groups) from strace
> sources
> Regenerate Linux syscall group info
>
> gdb/syscalls/aarch64-linux.xml | 26 +-
> gdb/syscalls/amd64-linux.xml | 106 ++---
> gdb/syscalls/arm-linux.xml | 26 +-
> gdb/syscalls/bfin-linux.xml | 26 +-
> gdb/syscalls/i386-linux.xml | 124 +++---
> gdb/syscalls/linux-defaults.xml.in | 545 ++++++++++++++++----------
> gdb/syscalls/mips-n32-linux.xml | 122 +++---
> gdb/syscalls/mips-n64-linux.xml | 100 ++---
> gdb/syscalls/mips-o32-linux.xml | 122 +++---
> gdb/syscalls/ppc-linux.xml | 124 +++---
> gdb/syscalls/ppc64-linux.xml | 104 ++---
> gdb/syscalls/s390-linux.xml | 122 +++---
> gdb/syscalls/s390x-linux.xml | 102 ++---
> gdb/syscalls/sparc-linux.xml | 114 +++---
> gdb/syscalls/sparc64-linux.xml | 94 ++---
> gdb/syscalls/update-linux-defaults.sh | 95 +++++
> 16 files changed, 1096 insertions(+), 856 deletions(-)
> create mode 100755 gdb/syscalls/update-linux-defaults.sh
>
>
> base-commit: 2e977d9901393ea1bacbe1896af0929e968bc811
next prev parent reply other threads:[~2023-02-25 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 23:26 Pedro Alves
2023-02-24 23:26 ` [PATCH 1/2] Autogenerate gdb/syscalls/linux-defaults.xml.in (groups) " Pedro Alves
2023-02-25 3:00 ` Simon Marchi
2023-02-27 15:04 ` Pedro Alves
2023-02-24 23:26 ` [PATCH 2/2] Regenerate Linux syscall group info Pedro Alves
2023-02-25 9:31 ` Tom de Vries [this message]
2023-02-27 14:53 ` [PATCH 0/2] Autogenerate gdb/syscalls/linux-defaults.xml.in (syscall groups) from strace sources Pedro Alves
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=ed367bac-a7ea-b5ca-e1cc-39b249123726@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).