Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Cleber Rosa <crosa@redhat.com>
To: gdb-patches@sourceware.org
Cc: crosa@redhat.com, areis@redhat.com
Subject: [PATCH 2/4] GDBServer: give more complete usage information
Date: Sat, 21 Mar 2015 02:35:00 -0000	[thread overview]
Message-ID: <1426905265-8495-3-git-send-email-crosa@redhat.com> (raw)
In-Reply-To: <1426905265-8495-1-git-send-email-crosa@redhat.com>

--attach/--multi are currently only mentioned on the usage info first lines,
the meaning of PROG is completely absent and COMM/PID text is unstructured.

The words and structure chosen may not be perfect but IMHO this is an improvement.

gdb/gdbserver/ChangeLog:
2015-03-20  Cleber Rosa  <crosa@redhat.com>

	* server.c (gdbserver_usage): Reorganized the usage message.
---
 gdb/gdbserver/server.c | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/gdb/gdbserver/server.c b/gdb/gdbserver/server.c
index 618e457..9dec972 100644
--- a/gdb/gdbserver/server.c
+++ b/gdb/gdbserver/server.c
@@ -2997,10 +2997,18 @@ gdbserver_usage (FILE *stream)
 	   "\tgdbserver [OPTIONS] --attach COMM PID\n"
 	   "\tgdbserver [OPTIONS] --multi COMM\n"
 	   "\n"
-	   "COMM may either be a tty device (for serial debugging), or \n"
-	   "HOST:PORT to listen for a TCP connection.\n"
+	   "Start mode options:\n"
+	   "  --attach              Attach to a given process\n"
+	   "  --multi               Start server without a specific program, and\n"
+	   "                        only quit when explicitly commanded\n"
 	   "\n"
-	   "Options:\n"
+	   "    COMM                tty device (for serial debugging) or HOST:PORT\n"
+	   "                        to listen for a TCP connection\n"
+	   "    PROG                Path to program executable\n"
+	   "    PID                 Process ID to attach to\n"
+	   "    ARGS                Arguments to be passed to debugged program\n"
+	   "\n"
+	   "Other options:\n"
 	   "  --debug               Enable general debugging output.\n"
 	   "  --debug-format=opt1[,opt2,...]\n"
 	   "                        Specify extra content in debugging output.\n"
-- 
1.9.3


  parent reply	other threads:[~2015-03-21  2:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-21  2:35 [PATCH 0/4] GDBServer: introduce a dedicated stderr stream Cleber Rosa
2015-03-21  2:35 ` [PATCH 1/4] GDBServer: introduce a stderr stream dedicated to the server Cleber Rosa
2015-03-21  2:35 ` [PATCH 4/4] GDBServer: add 'monitor set server-stderr' command Cleber Rosa
2015-03-21  8:29   ` Eli Zaretskii
2015-03-23 20:09     ` Cleber Rosa
2015-03-21  2:35 ` Cleber Rosa [this message]
2015-03-21 17:05   ` [PATCH 2/4] GDBServer: give more complete usage information Pedro Alves
2015-03-24 14:15     ` Cleber Rosa
2015-03-31 14:44       ` Cleber Rosa
2015-04-01 10:10       ` Pedro Alves
2015-03-21  2:35 ` [PATCH 3/4] GDBServer: introduce --server-stderr command line option Cleber Rosa
2015-03-21  8:26   ` Eli Zaretskii
2015-03-23 18:51     ` Cleber Rosa
2015-03-23 19:12       ` Eli Zaretskii
2015-03-23 20:35         ` Cleber Rosa
2015-03-23 20:43           ` Eli Zaretskii
2015-03-21 15:05 ` [PATCH 0/4] GDBServer: introduce a dedicated stderr stream Pedro Alves
2015-03-24 17:07   ` Cleber Rosa
2015-04-01 11:17     ` 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=1426905265-8495-3-git-send-email-crosa@redhat.com \
    --to=crosa@redhat.com \
    --cc=areis@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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