Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: John Baldwin <jhb@FreeBSD.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v3 2/3] Add an optional "alias" attribute to syscall entries.
Date: Wed, 28 Nov 2018 18:00:00 -0000	[thread overview]
Message-ID: <24c28a03-e548-daac-1ad9-47d0f31eb13e@FreeBSD.org> (raw)
In-Reply-To: <83r2f5drm4.fsf@gnu.org>

On 11/28/18 9:44 AM, Eli Zaretskii wrote:
>> Cc: gdb-patches@sourceware.org
>> From: John Baldwin <jhb@FreeBSD.org>
>> Date: Wed, 28 Nov 2018 09:22:22 -0800
>>
>> Yes, I think this is better as well.  Eli, I don't know if other OS's will
>> make use of this feature.  Given Pedro's new text above, do you think it
>> should still be moved into a native section or should it stay in the the
>> syscall section?
> 
> I question the need to make this text more general than this feature
> will ever become.  But if Pedro thinks we will have similar aliases on
> other OSes, then sure, do it as Pedro suggests.

Oh, I was just referring to Pedro's version being shorter.  I'm fine with
moving it.  This is a bit longer as it restores a bit of the FreeBSD-specific
note about syscall ABIs but that seemed relevant when moving it:

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 944a2c4383..c60c2b80c4 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -22329,6 +22329,7 @@ configurations.
 * Cygwin Native::		Features specific to the Cygwin port
 * Hurd Native::                 Features specific to @sc{gnu} Hurd
 * Darwin::			Features specific to Darwin
+* FreeBSD::			Features specific to FreeBSD
 @end menu
 
 @node BSD libkvm Interface
@@ -23214,6 +23215,26 @@ better understand the cause of a fault.  The default is off.
 Show the current state of exceptions trapping.
 @end table
 
+@node FreeBSD
+@subsection FreeBSD
+@cindex FreeBSD
+
+When the ABI of a system call is changed in the FreeBSD kernel, this
+is implemented by leaving a compatibility system call using the old
+ABI at the existing number and allocating a new system call number for
+the version using the new ABI.  As a convenience, when a system call
+is caught by name, compatibility system calls are also caught.
+
+For example, FreeBSD 12 introduced a new variant of the @code{kevent}
+system call and catching the @code{kevent} system call by name catches
+both variants:
+
+@smallexample
+(@value{GDBP}) catch syscall kevent
+Catchpoint 1 (syscalls 'freebsd11_kevent' [363] 'kevent' [560])
+(@value{GDBP})
+@end smallexample
+
 
 @node Embedded OS
 @section Embedded Operating Systems


-- 
John Baldwin

                                                                            


  reply	other threads:[~2018-11-28 18:00 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 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 [this message]
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 3/3] Update the FreeBSD system call table to match FreeBSD 12.0 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
     [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=24c28a03-e548-daac-1ad9-47d0f31eb13e@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