From: John Baldwin <jhb@FreeBSD.org>
To: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 3/3] Update the FreeBSD system call table to match FreeBSD 12.0.
Date: Fri, 09 Nov 2018 17:36:00 -0000 [thread overview]
Message-ID: <7e77cc04-4e70-6977-0839-3aa197aa6f0d@FreeBSD.org> (raw)
In-Reply-To: <485c1c69-66b8-fd50-eea0-c8b5b8e0fea5@redhat.com>
On 11/9/18 8:34 AM, Pedro Alves wrote:
> On 11/06/2018 05:54 PM, John Baldwin 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.
>
> Can you make the script emit the usual make-read-only trick at the
> top of the generated file?
I ended up having to do it in a kind of ugly way to get a file that
libexpat would parse and Emacs would still recognize as read-only.
This version libexpat failed to parse:
<!-- THIS FILE IS GENERATED -*- buffer-read-only: t -*- -->
<!-- vi:set ro: -->
<?xml version="1.0"?>
This version Emacs didn't mark read-only:
<?xml version="1.0"?>
<!-- THIS FILE IS GENERATED -*- buffer-read-only: t -*- -->
<!-- vi:set ro: -->
So I'm using this:
<?xml version="1.0"?> <!-- THIS FILE IS GENERATED -*- buffer-read-only: t -*- -->
<!-- vi:set ro: -->
I haven't tested in vim though.
>> +++ b/gdb/syscalls/update-freebsd.sh
>> @@ -0,0 +1,77 @@
>> +#! /bin/sh
>> +
>> +# Copyright (C) 2011-2018 Free Software Foundation, Inc.
>
> Curious, you had this script since 2011?
Oops, I just copied the license block from update-gnulib.sh I think. Fixed.
--
John Baldwin
                                                                           Â
next prev parent reply other threads:[~2018-11-09 17:36 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
2018-11-09 16:34 ` Pedro Alves
2018-11-09 17:36 ` John Baldwin [this message]
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 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 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=7e77cc04-4e70-6977-0839-3aa197aa6f0d@FreeBSD.org \
--to=jhb@freebsd.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).