From: John Baldwin <jhb@FreeBSD.org>
To: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 1/3] Return a vector of integers from get_syscalls_by_group.
Date: Fri, 09 Nov 2018 17:55:00 -0000 [thread overview]
Message-ID: <77fb9e1d-a1fa-9c09-df33-bb237af66ef9@FreeBSD.org> (raw)
In-Reply-To: <20181108212741.0efc6278@pinnacle.lan>
On 11/8/18 8:27 PM, Kevin Buettner wrote:
> On Tue, 6 Nov 2018 09:54:29 -0800
> John Baldwin <jhb@FreeBSD.org> wrote:
>
>> This removes the need for the caller to explicitly manage the memory
>> for the returned system call list. This change only returns the
>> numbers rather than a vector of syscall structures since the caller
>> only needs the numbers.
>>
>> gdb/ChangeLog:
>>
>> * break-catch-syscall.c (catch_syscall_split_args): Update for
>> get_syscalls_by_group returning a vector.
>> * xml-syscall.c [!HAVE_LIBEXPATH] (get_syscalls_by_group): Return
>
> s/HAVE_LIBEXPATH/HAVE_LIBEXPAT/
Thanks, will be fixed in v3.
--
John Baldwin
                                                                           Â
next prev parent reply other threads:[~2018-11-09 17:55 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 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 [this message]
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 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 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=77fb9e1d-a1fa-9c09-df33-bb237af66ef9@FreeBSD.org \
--to=jhb@freebsd.org \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@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