From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: John Baldwin <jhb@FreeBSD.org>
Subject: Re: [PATCH v2 3/3] Update the FreeBSD system call table to match FreeBSD 12.0.
Date: Fri, 09 Nov 2018 04:38:00 -0000 [thread overview]
Message-ID: <20181108213828.446393a8@pinnacle.lan> (raw)
In-Reply-To: <20181106175431.59832-4-jhb@FreeBSD.org>
On Tue, 6 Nov 2018 09:54:31 -0800
John Baldwin <jhb@FreeBSD.org> wrote:
> Add a script to generate the FreeBSD XML system call table from the
> sys/sys/syscall.h file in the kernel source tree. For ABI
> compatiblity system calls used by older binaries (such as
> freebsd11_kevent()), the original system call name is used as an
> alias.
>
> Run this script against the current syscall.h file in FreeBSD's head
> branch which is expected to be the file used in 12.0 (head is
> currently in code freeze as part of the 12.0 release process).
>
> gdb/ChangeLog:
>
> * syscalls/update-freebsd.sh: New file.
> * syscalls/freebsd.xml: Regenerate.
LGTM.
Kevin
next prev parent reply other threads:[~2018-11-09 4:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 17:56 [PATCH v2 0/3] Update FreeBSD's syscall table 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 [this message]
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 ` [PATCH v2 0/3] Update FreeBSD's syscall table Sergio Durigan Junior
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=20181108213828.446393a8@pinnacle.lan \
--to=kevinb@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