Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb] Add gdb/syscalls/Makefile
Date: Mon, 9 May 2022 16:46:56 +0200	[thread overview]
Message-ID: <8e46617e-387a-1d9f-3f27-fa23571aa16a@suse.de> (raw)
In-Reply-To: <129577b3-8c3a-a0c3-e4e3-046873f048bb@simark.ca>

On 5/9/22 16:41, Simon Marchi wrote:
> On 2022-05-09 06:26, Tom de Vries via Gdb-patches wrote:
>> [ Re: [PATCH][gdb/tdep] Support catch syscall pipe2 for i386 ]
>>
>> On 5/5/22 15:20, Simon Marchi wrote:
>>>> [gdb/tdep] Support catch syscall pipe2 for i386
>>>>
>>>> With test-case gdb.base/catch-syscall.exp and target board unix/-m32, we run
>>>> into:
>>>> ...
>>>> (gdb) catch syscall pipe2^M
>>>> Unknown syscall name 'pipe2'.^M
>>>> (gdb) FAIL: gdb.base/catch-syscall.exp: determine pipe syscall: catch syscall pipe2
>>>> ...
>>>>
>>>> Fix this by:
>>>> - adding a pipe2 entry in gdb/syscalls/i386-linux.xml.in, and
>>>> - regenerating gdb/syscalls/i386-linux.xml using
>>>>     "xsltproc --output i386-linux.xml apply-defaults.xsl i386-linux.xml.in".
>>>      
>>> The patch LGTM, assuming this is the right number for pipe2 :).
>>>
>>
>> Thanks for the review, committed.
>>
>> And, I'd say, yes, the correct number:
>> ...
>> $ grep pipe2 ./arch/x86/entry/syscalls/syscall_32.tbl
>> 331     i386    pipe2                   sys_pipe2
>> ...
>>
>>> I suppose we are missing more syscalls than that, given that new
>>> syscalls are added regularly, e.g. rseq:
>>>
>>>     https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d7822b1e24f2
>>>
>>> As long as rseq is not listed in this file, it means a user wouldn't be
>>> able to use "catch syscall rseq", I suppose?  We would need a procedure
>>> to add new syscalls periodically.
>>>
>>> Could we add a simple Makefile (as a separate patch) that contains these
>>> xslt commands?  I think you searched a little bit how those files were
>>> originally generated, so it would be nice to save the trouble in the
>>> future.
>>
>> Good idea, how about this?
>>
>> Thanks,
>> - Tom
> 
> LGTM.  I would probably use a hand-written list of files in the Makefile
> rather than the "shell ls", but it the end it doesn't matter much.

Ack, committed ... and CC-ing bfin authorized committer about the new 
gdb/syscalls/bfin-linux.xml file.

Thanks,
- Tom

  reply	other threads:[~2022-05-09 14:49 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 [this message]
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
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=8e46617e-387a-1d9f-3f27-fa23571aa16a@suse.de \
    --to=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --cc=tdevries@suse.de \
    /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