From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
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>
Subject: [doc] NEWS: QCatchSyscalls: simplify
Date: Sun, 29 May 2016 16:47:00 -0000 [thread overview]
Message-ID: <20160529164745.GA21714@host1.jankratochvil.net> (raw)
In-Reply-To: <1452308954-13679-1-git-send-email-jistone@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
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?
Thanks,
Jan
[-- Attachment #2: 1 --]
[-- Type: text/plain, Size: 1220 bytes --]
gdb/ChangeLog
2016-05-29 Jan Kratochvil <jan.kratochvil@redhat.com>
* NEWS (QCatchSyscalls): Remove the parameter. Include ...
(QCatchSyscalls:1 in qSupported) ... this separate entry which got
deleted.
diff --git a/gdb/NEWS b/gdb/NEWS
index f874f03..dce79a2 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -250,10 +250,9 @@ 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.
+QCatchSyscalls
+ Enables/disables catching syscalls from the inferior process.
+ The remote stub reports support for this packet to GDB's qSupported query.
syscall_entry stop reason
Indicates that a syscall was just called.
@@ -261,10 +260,6 @@ syscall_entry stop reason
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.
next prev parent reply other threads:[~2016-05-29 16:47 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 11:02 [PATCH] Implement 'catch syscall' for gdbserver Josh Stone
2015-10-30 13:26 ` Eli Zaretskii
2015-11-01 22:15 ` Doug Evans
2015-11-02 18:24 ` Josh Stone
2015-11-21 10:29 ` Philippe Waroquiers
2015-11-23 4:20 ` Doug Evans
2015-11-23 4:20 ` Doug Evans
2015-11-25 2:37 ` Josh Stone
2015-11-26 2:53 ` [PATCH v2 1/2] gdbserver: Set Linux ptrace options ASAP Josh Stone
2015-11-26 2:54 ` [PATCH v2 2/2] Implement 'catch syscall' for gdbserver Josh Stone
2015-11-26 10:34 ` [PATCH v2 1/2] gdbserver: Set Linux ptrace options ASAP Pedro Alves
2015-11-30 18:50 ` Josh Stone
2015-12-01 20:17 ` Josh Stone
2015-12-02 14:01 ` Pedro Alves
2015-12-04 2:26 ` [PATCH v3 1/2] gdbserver: set ptrace flags after creating inferiors Josh Stone
2015-12-04 2:27 ` [PATCH v3 2/2] Implement 'catch syscall' for gdbserver Josh Stone
2015-12-04 8:45 ` Eli Zaretskii
2015-12-05 2:14 ` Josh Stone
2015-12-05 8:02 ` Eli Zaretskii
2015-12-07 16:50 ` Josh Stone
2015-12-07 17:15 ` Eli Zaretskii
2015-12-04 13:18 ` Pedro Alves
2015-12-05 2:16 ` Josh Stone
2015-12-08 13:31 ` Pedro Alves
2015-12-08 19:02 ` Josh Stone
2015-12-08 13:37 ` Pedro Alves
2015-12-11 21:19 ` Josh Stone
2015-12-16 15:42 ` Pedro Alves
2016-01-09 3:09 ` [PATCH v4] " Josh Stone
2016-01-09 7:37 ` Eli Zaretskii
2016-01-11 17:44 ` Philippe Waroquiers
2016-01-12 12:05 ` Pedro Alves
2016-01-12 19:10 ` Josh Stone
2016-01-12 19:22 ` Pedro Alves
2016-01-12 20:01 ` Josh Stone
2016-03-29 14:27 ` Yao Qi
2016-03-29 18:12 ` Josh Stone
2016-03-29 23:49 ` Josh Stone
2016-03-30 12:23 ` Yao Qi
2016-03-31 1:10 ` Josh Stone
2016-04-01 13:05 ` Yao Qi
2016-04-01 16:38 ` Josh Stone
2016-05-29 16:47 ` Jan Kratochvil [this message]
2016-05-29 17:29 ` [doc] NEWS: QCatchSyscalls: simplify Eli Zaretskii
2016-05-29 17:50 ` Jan Kratochvil
2016-05-29 18:19 ` Eli Zaretskii
2016-05-29 18:47 ` [commit] " Jan Kratochvil
2015-12-04 12:16 ` [PATCH v3 1/2] gdbserver: set ptrace flags after creating inferiors Pedro Alves
2015-12-05 2:14 ` Josh Stone
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=20160529164745.GA21714@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jistone@redhat.com \
--cc=palves@redhat.com \
--cc=philippe.waroquiers@skynet.be \
--cc=scox@redhat.com \
--cc=sergiodj@redhat.com \
--cc=xdje42@gmail.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).