From: John Baldwin <jhb@FreeBSD.org>
To: Pedro Alves <palves@redhat.com>, Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3 2/3] Add an optional "alias" attribute to syscall entries.
Date: Tue, 27 Nov 2018 21:54:00 -0000 [thread overview]
Message-ID: <650590ef-3036-57a8-6cd5-abaa5654add3@FreeBSD.org> (raw)
In-Reply-To: <b54a5e80-76a6-d2dd-45d3-b93b7be065c1@redhat.com>
On 11/27/18 9:13 AM, Pedro Alves wrote:
> On 11/09/2018 08:18 PM, Eli Zaretskii wrote:
>>> From: John Baldwin <jhb@FreeBSD.org>
>>> Date: Fri, 9 Nov 2018 12:04:31 -0800
>>>
>>> diff --git a/gdb/NEWS b/gdb/NEWS
>>> index ff9b192a38..ff225f361e 100644
>>> --- a/gdb/NEWS
>>> +++ b/gdb/NEWS
>>> @@ -38,6 +38,11 @@
>>> requires the use of a keyword. Selecting a frame by level is
>>> unchanged. The MI comment "-stack-select-frame" is unchanged.
>>>
>>> +* System call catchpoints now support system call aliases. This is
>>> + used with the FreeBSD system call list so that system call
>>> + catchpoints will also trigger for legacy system call numbers used by
>>> + older FreeBSD binaries.
>>
>> IMO, this is very abstract and too vague to be useful. Since we won't
>> have anything more detailed in the manual, would it be possible to
>> make this description more concrete? E.g., how about using some of
>> the text and examples you used in your description of the issue:
>
> Should we, have something in the manual?
Hmm, here's a patch I came up with for the manual:
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 944a2c4383..ab4fad3c36 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -4683,6 +4683,22 @@ Catchpoint 2 (syscall 764)
(@value{GDBP})
@end smallexample
+On some operating systems, a system call name may map to more than one
+system call number. For example, the FreeBSD kernel allocates new
+system call numbers when changing the ABI of an existing system call.
+The kernel also includes a compatibility system call using the old ABI
+and number. FreeBSD's system call XML file includes aliases for
+compatibility system calls that are used to catch all versions of a
+system call. For example, FreeBSD 12 introduced a new variant of the
+@code{kevent} system call. Both system calls are caught when catching
+the @code{kevent} system call:
+
+@smallexample
+(@value{GDBP}) catch syscall kevent
+Catchpoint 1 (syscalls 'freebsd11_kevent' [363] 'kevent' [560])
+(@value{GDBP})
+@end smallexample
+
If you configure @value{GDBN} using the @samp{--without-expat} option,
it will not be able to display syscall names. Also, if your
architecture does not have an XML file describing its system calls,
--
John Baldwin
                                                                           Â
next prev parent reply other threads:[~2018-11-27 21:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 20:04 [PATCH v3 0/3] Update FreeBSD's syscall table John Baldwin
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
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 [this message]
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
[not found] ` <7ffda341-7706-d541-939e-f45a7a3f9bd7@FreeBSD.org>
2018-11-27 17:20 ` [PATCH v3 0/3] Update FreeBSD's syscall table Pedro Alves
2018-11-27 20:00 ` 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=650590ef-3036-57a8-6cd5-abaa5654add3@FreeBSD.org \
--to=jhb@freebsd.org \
--cc=eliz@gnu.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