From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simark@simark.ca>
Subject: Re: [PATCH][gdb] Update syscalls/{amd64,i386}-linux.xml
Date: Mon, 16 May 2022 10:07:19 -0600 [thread overview]
Message-ID: <87ee0tea14.fsf@tromey.com> (raw)
In-Reply-To: <22cb80d8-3537-1d66-c54a-3e46630460dc@suse.de> (Tom de Vries via Gdb-patches's message of "Tue, 10 May 2022 13:53:37 +0200")
>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> On 5/9/22 12:39, Tom de Vries wrote:
>> [ FWIW, it seems the linux kernel migrated to some syscall.tbl
>> approach, and perhaps generating from there could be an option. ]
Tom> Well, I gave that a try, in a separate script update-linux-2.sh
Tom> (haven't though of a good name yet).
Tom> Any comments?
Maybe it should just replace update-linux.sh?
Tom> In particular, there are a few new "reserved<n>" and "unused<n>"
Tom> entries that don't look problematic to me, but perhaps these should be
Tom> filtered out.
I think it seems better to skip them.
Anyway if this is the direction Linux is going, like if this .tbl file
is some authoritative source, then I think it makes the most sense for
gdb to follow.
Tom
next prev parent reply other threads:[~2022-05-16 16:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 14:57 [PATCH][gdb/testsuite] Handle pipe2 syscall in gdb.base/catch-syscall.exp Tom de Vries via Gdb-patches
2022-05-05 11:47 ` [PATCH, v2][gdb/testsuite] " Tom de Vries via Gdb-patches
2022-05-05 11:49 ` [PATCH][gdb/tdep] Support catch syscall pipe2 for i386 Tom de Vries via Gdb-patches
2022-05-05 13:20 ` Simon Marchi via Gdb-patches
2022-05-09 10:26 ` [PATCH][gdb] Add gdb/syscalls/Makefile Tom de Vries via Gdb-patches
2022-05-09 14:41 ` Simon Marchi via Gdb-patches
2022-05-09 14:46 ` Tom de Vries via Gdb-patches
2022-05-09 10:39 ` [PATCH][gdb] Update syscalls/{amd64,i386}-linux.xml Tom de Vries via Gdb-patches
2022-05-09 14:48 ` Simon Marchi via Gdb-patches
2022-05-09 15:29 ` Tom de Vries via Gdb-patches
2022-05-09 15:40 ` Andreas Schwab
2022-05-09 15:42 ` Tom de Vries via Gdb-patches
2022-05-09 15:45 ` Andreas Schwab
2022-05-09 16:04 ` Tom de Vries via Gdb-patches
2022-05-09 17:19 ` Tom Tromey
2022-05-10 11:39 ` Tom de Vries via Gdb-patches
2022-05-12 9:00 ` Tom de Vries via Gdb-patches
2022-05-10 11:53 ` Tom de Vries via Gdb-patches
2022-05-16 16:07 ` Tom Tromey [this message]
2022-05-18 9:58 ` [committed][gdb/tdep] Add gdb/syscalls/update-linux-from-src.sh Tom de Vries via Gdb-patches
2022-05-05 13:23 ` [PATCH, v2][gdb/testsuite] Handle pipe2 syscall in gdb.base/catch-syscall.exp Simon Marchi via Gdb-patches
2022-05-09 10:18 ` Tom de Vries via Gdb-patches
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=87ee0tea14.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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