This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [doc] NEWS: QCatchSyscalls: simplify
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: gdb-patches at sourceware dot org, philippe dot waroquiers at skynet dot be, sergiodj at redhat dot com, palves at redhat dot com, xdje42 at gmail dot com, scox at redhat dot com, jistone at redhat dot com
- Date: Sun, 29 May 2016 20:29:19 +0300
- Subject: Re: [doc] NEWS: QCatchSyscalls: simplify
- Authentication-results: sourceware.org; auth=none
- References: <1449196006-13759-2-git-send-email-jistone at redhat dot com> <1452308954-13679-1-git-send-email-jistone at redhat dot com> <20160529164745 dot GA21714 at host1 dot jankratochvil dot net>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Sun, 29 May 2016 18:47:45 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org, philippe.waroquiers@skynet.be,
> sergiodj@redhat.com, palves@redhat.com, eliz@gnu.org, xdje42@gmail.com,
> scox@redhat.com, Josh Stone <jistone@redhat.com>
>
> On Sat, 09 Jan 2016 04:09:14 +0100, Josh Stone wrote:
> > --- a/gdb/NEWS
> > +++ b/gdb/NEWS
> > @@ -120,6 +120,21 @@ N stop reply
> > threads are stopped). The remote stub reports support for this stop
> > reply to GDB's qSupported query.
> >
> > +QCatchSyscalls:1 [;SYSNO]...
> > +QCatchSyscalls:0
> > + Enable ("QCatchSyscalls:1") or disable ("QCatchSyscalls:0")
> > + catching syscalls from the inferior process.
> > +
> > +syscall_entry stop reason
> > + Indicates that a syscall was just called.
> > +
> > +syscall_return stop reason
> > + Indicates that a syscall just returned.
> > +
> > +QCatchSyscalls:1 in qSupported
> > + The qSupported packet may now include QCatchSyscalls:1 in the reply
> > + to indicate support for catching syscalls.
> > +
> > * Extended-remote exec events
> >
> > ** GDB now has support for exec events on extended-remote Linux targets.
>
> I find this format non-standard/confusing. OK to check-in this update?
Is it really that bad? I generally tend to let people say things in
their own words, as long as it's readable. But if you insist...