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: Wed, 07 Nov 2007 22:06:00 -0000 [thread overview]
Message-ID: <ubqa5r9rb.fsf@gnu.org> (raw)
In-Reply-To: <20071107211833.GA28200@caradoc.them.org> (message from Daniel Jacobowitz on Wed, 7 Nov 2007 16:18:33 -0500)
> Date: Wed, 7 Nov 2007 16:18:33 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> I don't think this behavior is useful. "run" should select a native
> target when the current target is an executable or core file, but
> not when it's connected to some other target. This patch changes
> the behavior to:
>
> (gdb) run
> The "remote" target can not run programs. Try "help target" or "continue".
>
> Any comments? Shall I commit this?
I'm okay with the change, but how do you feel about updating the docs
as well? Should we?
next prev parent reply other threads:[~2007-11-07 22:06 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 [this message]
2007-11-07 22:17 ` Daniel Jacobowitz
2007-11-17 11:32 ` Eli Zaretskii
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=ubqa5r9rb.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