From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13483 invoked by alias); 6 Apr 2013 06:47:33 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 13474 invoked by uid 89); 6 Apr 2013 06:47:33 -0000 X-Spam-SWARE-Status: No, score=-7.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.1 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Sat, 06 Apr 2013 06:47:31 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r366lT3x029385 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 6 Apr 2013 02:47:29 -0400 Received: from host2.jankratochvil.net (ovpn-116-44.ams2.redhat.com [10.36.116.44]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r366lPCu002001 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sat, 6 Apr 2013 02:47:28 -0400 Date: Sat, 06 Apr 2013 15:04:00 -0000 From: Jan Kratochvil To: Eli Zaretskii Cc: gdb-patches@sourceware.org Subject: Re: [doc patch] gdbserver.1: Document all the options and --multi Message-ID: <20130406064724.GA483@host2.jankratochvil.net> References: <20130405181316.GA3675@host2.jankratochvil.net> <83ppy8es8n.fsf@gnu.org> <20130405202033.GA11174@host2.jankratochvil.net> <83k3ogdvzg.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83k3ogdvzg.fsf@gnu.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes X-SW-Source: 2013-04/txt/msg00151.txt.bz2 On Sat, 06 Apr 2013 08:16:51 +0200, Eli Zaretskii wrote: > > +@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 ...". I do not think it would be good, (1) the --multi mode is IMO an unusual one, a special case and (2) I also tried to generally keep the "gdbserver --help" output order. Thanks, Jan