From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] Add "set remote multiprocess-extensions-packet" command
Date: Mon, 24 Aug 2015 17:28:00 -0000 [thread overview]
Message-ID: <8337z8h9zn.fsf@gnu.org> (raw)
In-Reply-To: <1440436237-24015-2-git-send-email-palves@redhat.com>
> From: Pedro Alves <palves@redhat.com>
> Date: Mon, 24 Aug 2015 18:10:36 +0100
>
> +set remote multiprocess-extensions-packet
> +show remote multiprocess-extensions--packet
^^
Extra hyphen.
> gdb/doc/ChangeLog:
> 2015-08-24 Pedro Alves <palves@redhat.com>
>
> * gdb.texinfo (Remote Configuration): Document the "set/show
> remote multiprocess-extensions-packet" commands.
What the ChangeLog entry promises the text doesn't keep:
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index 5dfb14b..cd0abad 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -20205,6 +20205,10 @@ are:
> @tab @code{Z0 and Z1}
> @tab @code{Support for target-side breakpoint condition evaluation}
>
> +@item @code{multiprocess-extensions}
> +@tab @code{multiprocess extensions}
> +@tab Debug multiple processes and remote process PID awareness
> +
> @item @code{swbreak-feature}
> @tab @code{swbreak stop reason}
> @tab @code{break}
Thanks.
next prev parent reply other threads:[~2015-08-24 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 17:10 [PATCH 0/2] Fix gdbserver crash on all non-GNU/Linux targets Pedro Alves
2015-08-24 17:10 ` [PATCH 1/2] Add "set remote multiprocess-extensions-packet" command Pedro Alves
2015-08-24 17:28 ` Eli Zaretskii [this message]
2015-08-24 17:31 ` Pedro Alves
2015-08-24 17:34 ` Eli Zaretskii
2015-08-24 17:10 ` [PATCH 2/2] gdbserver crashes when multiprocess extensions aren't supported Pedro Alves
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=8337z8h9zn.fsf@gnu.org \
--to=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