Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: John Baldwin <jhb@FreeBSD.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 0/3] Update FreeBSD's syscall table
Date: Tue, 06 Nov 2018 18:49:00 -0000	[thread overview]
Message-ID: <87pnvi2gbf.fsf@redhat.com> (raw)
In-Reply-To: <20181106175431.59832-1-jhb@FreeBSD.org> (John Baldwin's message	of "Tue, 6 Nov 2018 09:54:28 -0800")

On Tuesday, November 06 2018, John Baldwin wrote:

> Relative to the first version of this patch series, I've fixed some
> nits noted by reviewers.  One thing I have not changed is I chose to
> keep the changed API of returning a vector of integers from
> get_syscalls_by_name().  I have expanded the comment in xml-syscall.h
> a bit to be more clear on why it returns a vector of integers.
>
> I also added a new patch (patch 1) to change the similar
> get_syscalls_by_group() to return a vector of integers instead of an
> allocated array of structures.  This results in more symmetry in the
> final code in break-catch-syscall.c.  There wasn't a very clean way to
> share the bits of duplicated code however.

I've read the patch series again, and it looks fine to me.  I'm still
not 100% happy with get_syscalls_by_name returning a vector, but this is
a minor thing (and a personal preference) and shouldn't block the patch.
Thanks for addressing the comments I've made, and sorry for not replying
to you e-mail (for some reason, I didn't get it in my INBOX).

I am not a global maintainer, BTW.

> John Baldwin (3):
>   Return a vector of integers from get_syscalls_by_group.
>   Add an optional "alias" attribute to syscall entries.
>   Update the FreeBSD system call table to match FreeBSD 12.0.
>
>  gdb/ChangeLog                  |  37 ++++++++++++
>  gdb/break-catch-syscall.c      |  27 ++++-----
>  gdb/gdbarch.h                  |   3 -
>  gdb/gdbarch.sh                 |   3 -
>  gdb/syscalls/freebsd.xml       | 107 ++++++++++++++++++++++++++-------
>  gdb/syscalls/gdb-syscalls.dtd  |   1 +
>  gdb/syscalls/update-freebsd.sh |  77 ++++++++++++++++++++++++
>  gdb/xml-syscall.c              |  91 ++++++++++++----------------
>  gdb/xml-syscall.h              |  17 +++---
>  9 files changed, 258 insertions(+), 105 deletions(-)
>  create mode 100755 gdb/syscalls/update-freebsd.sh
>
> -- 
> 2.18.0

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


      parent reply	other threads:[~2018-11-06 18:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 17:56 John Baldwin
2018-11-06 17:56 ` [PATCH v2 3/3] Update the FreeBSD system call table to match FreeBSD 12.0 John Baldwin
2018-11-09  4:38   ` Kevin Buettner
2018-11-09 16:34   ` Pedro Alves
2018-11-09 17:36     ` John Baldwin
2018-11-06 17:56 ` [PATCH v2 2/3] Add an optional "alias" attribute to syscall entries John Baldwin
2018-11-09  4:34   ` Kevin Buettner
2018-11-09 15:28   ` Simon Marchi
2018-11-09 15:36     ` Simon Marchi
2018-11-09 16:31   ` Pedro Alves
2018-11-09 16:52     ` John Baldwin
2018-11-06 17:56 ` [PATCH v2 1/3] Return a vector of integers from get_syscalls_by_group John Baldwin
2018-11-09  4:27   ` Kevin Buettner
2018-11-09 17:55     ` John Baldwin
2018-11-06 18:49 ` Sergio Durigan Junior [this message]

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=87pnvi2gbf.fsf@redhat.com \
    --to=sergiodj@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