Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: John Baldwin <jhb@FreeBSD.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH v3 0/3] Update FreeBSD's syscall table
Date: Tue, 27 Nov 2018 17:20:00 -0000	[thread overview]
Message-ID: <b7bdfebb-3f6d-3674-3b29-608c07fff2e6@redhat.com> (raw)
In-Reply-To: <7ffda341-7706-d541-939e-f45a7a3f9bd7@FreeBSD.org>

On 11/26/2018 08:31 PM, John Baldwin wrote:
> On 11/9/18 12:04 PM, John Baldwin wrote:
>> Relative to V2, this changes the "get syscalls" functions to pass in
>> an integer vector by reference to append syscall numbers to.  It also
>> adds a NEWS entry and fixes some other nits noted by reviewers on the
>> V2 series.
>>
>> John Baldwin (3):
>>   Change get_syscalls_by_group to append to an existing vector of
>>     integers.
>>   Add an optional "alias" attribute to syscall entries.
>>   Update the FreeBSD system call table to match FreeBSD 12.0.
>>
>>  gdb/ChangeLog                  |  41 ++++++++++++
>>  gdb/NEWS                       |   5 ++
>>  gdb/break-catch-syscall.c      |  25 ++------
>>  gdb/gdbarch.h                  |   3 -
>>  gdb/gdbarch.sh                 |   3 -
>>  gdb/syscalls/freebsd.xml       | 110 ++++++++++++++++++++++++++-------
>>  gdb/syscalls/gdb-syscalls.dtd  |   1 +
>>  gdb/syscalls/update-freebsd.sh |  78 +++++++++++++++++++++++
>>  gdb/xml-syscall.c              | 108 ++++++++++++++++----------------
>>  gdb/xml-syscall.h              |  20 +++---
>>  10 files changed, 279 insertions(+), 115 deletions(-)
>>  create mode 100755 gdb/syscalls/update-freebsd.sh
> 
> Ping?  Eli signed off on an updated NEWS entry earlier in the thread.  Any
> further comments on the code changes?
This looks good to me, though there's the issue with the non-const
references discussed here:

  https://sourceware.org/ml/gdb-patches/2018-11/msg00351.html
  https://sourceware.org/ml/gdb-patches/2018-11/msg00441.html
  https://sourceware.org/ml/gdb-patches/2018-11/msg00443.html
  https://sourceware.org/ml/gdb-patches/2018-11/msg00444.html

BTW:

> -  <syscall name="mknodat" number="498"/>
> +  <syscall name="freebsd11_mknodat" number="498" alias="mknodat"/>
> ...
> +  <syscall name="mknodat" number="559"/>

Does "catch syscall 498" catch only freebsd11_mknodat calls, or do
we for some reason end up catching calls to 559 as well?
I'd expect only 498.  What about "catch syscall 559"?

Thanks,
Pedro Alves


  parent reply	other threads:[~2018-11-27 17:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 20:04 John Baldwin
2018-11-09 20:04 ` [PATCH v3 2/3] Add an optional "alias" attribute to syscall entries John Baldwin
2018-11-09 20:18   ` Eli Zaretskii
2018-11-16 17:44     ` John Baldwin
2018-11-16 19:37       ` Eli Zaretskii
2018-11-27 17:13     ` Pedro Alves
2018-11-27 21:54       ` John Baldwin
2018-11-28  6:31         ` Eli Zaretskii
     [not found]         ` <34fcc769-4533-31bf-d258-36c6110037e0@redhat.com>
2018-11-28 17:22           ` John Baldwin
2018-11-28 17:44             ` Eli Zaretskii
2018-11-28 18:00               ` John Baldwin
2018-11-28 18:31                 ` Eli Zaretskii
2018-11-28 18:34                 ` Pedro Alves
2018-11-28 19:15                   ` John Baldwin
2018-11-28 19:21                   ` Eli Zaretskii
2018-11-09 20:04 ` [PATCH v3 1/3] Change get_syscalls_by_group to append to an existing vector of integers John Baldwin
2018-11-09 20:04 ` [PATCH v3 3/3] Update the FreeBSD system call table to match FreeBSD 12.0 John Baldwin
     [not found] ` <7ffda341-7706-d541-939e-f45a7a3f9bd7@FreeBSD.org>
2018-11-27 17:20   ` Pedro Alves [this message]
2018-11-27 20:00     ` [PATCH v3 0/3] Update FreeBSD's syscall table John Baldwin

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=b7bdfebb-3f6d-3674-3b29-608c07fff2e6@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@FreeBSD.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