From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-100224-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 4399 invoked by alias); 6 Apr 2013 06:16:55 -0000
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
Received: (qmail 4387 invoked by uid 89); 6 Apr 2013 06:16:54 -0000
X-Spam-SWARE-Status: No, score=-4.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,SPF_SOFTFAIL autolearn=no version=3.3.1
Received: from mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172)    by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Sat, 06 Apr 2013 06:16:50 +0000
Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0MKT00K00LB1Y400@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Sat, 06 Apr 2013 09:16:48 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MKT00KGYLG0Y700@a-mtaout22.012.net.il>; Sat, 06 Apr 2013 09:16:48 +0300 (IDT)
Date: Sat, 06 Apr 2013 13:56:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [doc patch] gdbserver.1: Document all the options and --multi
In-reply-to: <20130405202033.GA11174@host2.jankratochvil.net>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83k3ogdvzg.fsf@gnu.org>
References: <20130405181316.GA3675@host2.jankratochvil.net> <83ppy8es8n.fsf@gnu.org> <20130405202033.GA11174@host2.jankratochvil.net>
X-SW-Source: 2013-04/txt/msg00150.txt.bz2

> Date: Fri, 5 Apr 2013 22:20:33 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org
> 
> +The three mode of executing @command{gdbserver} have the following options.
             ^^^^
"modes"

> +@table @env
> +
> +@item gdbserver @var{comm} @var{prog} [@var{args}@dots{}]
> +For the @var{comm} parameter see below, then supply name of the program to
> +debug; the remote @value{GDBN} will do everything else.  Any remaining
> +arguments will be passed to the program verbatim.
> +
> +@item gdbserver --attach @var{comm} @var{pid}
> +For the @var{comm} parameter see below, then supply @var{pid} of a running
> +program; @value{GDBN} will do everything else.
> +
> +@item gdbserver --multi @var{comm}
> +For the @var{comm} parameter see below; @value{GDBN} can then instruct
> +@command{gdbserver} which command(s) to run.
> +
> +@end table
> +
> +The @var{comm} parameter  is either a device name (to use a serial line),
> +or a TCP portnumber (string @code{:1234}), or @code{-} or @code{stdio} to use
> +stdin/stdout of @code{gdbserver}.

This is OK, but perhaps will be even better if you describe the last
mode first.  Then you can put the description of @var{comm} there, and
in the other 2 modes say something like "In addition to @var{comm} as
above, supply ...".

No other comments, thanks.