Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Stop unlikely "run"'s earlier
Date: Sat, 17 Nov 2007 11:32:00 -0000	[thread overview]
Message-ID: <ud4u9cdkv.fsf@gnu.org> (raw)
In-Reply-To: <20071107221730.GA31647@caradoc.them.org> (message from Daniel 	Jacobowitz on Wed, 7 Nov 2007 17:17:30 -0500)

> Date: Wed, 7 Nov 2007 17:17:30 -0500
> From: Daniel Jacobowitz <drow@false.org>
> 
> On Thu, Nov 08, 2007 at 12:06:16AM +0200, Eli Zaretskii wrote:
> > I'm okay with the change, but how do you feel about updating the docs
> > as well?  Should we?
> 
> I just looked at the description of "run" in the manual.  If anything,
> this patch brings GDB better in line with its manual, but if you can
> think of a way to describe the difference I'm all ears.

Well, under "target remote" (in the node "Connecting") we say:

    Once the connection has been established, you can use all the usual
    commands to examine and change data and to step and continue the
    remote program.

Given you description, I'd say this should be augmented by explaining
that the program is already running at this stage, and telling the
user to use "continue", as opposed to "run" in local debugging.

Also, under "run" (in node "Starting"), it'd be a good thing to cite
the error message you want top introduce:

  The "remote" target can not run programs.  Try "help target" or "continue".

and tell the reader that the most probable cause here is that "run"
was used rather than "continue".  Without such an explanation, I'd be
quite lost if I saw this message (what do you mean ``can't run''? how
can I debug the darn thing it it cannot be run?)

WDYT?


  reply	other threads:[~2007-11-17 11:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-07 21:18 Daniel Jacobowitz
2007-11-07 22:06 ` Eli Zaretskii
2007-11-07 22:17   ` Daniel Jacobowitz
2007-11-17 11:32     ` Eli Zaretskii [this message]
2008-02-27 20:32       ` Daniel Jacobowitz
2008-02-27 21:29         ` Eli Zaretskii
2008-02-28 16:28           ` Daniel Jacobowitz
2007-11-07 23:44 ` Joel Brobecker

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=ud4u9cdkv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --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