From: Todd Whitesel <toddpw@best.com>
To: tromey@redhat.com
Cc: david@llamedos.org, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] specify arguments to debugee from commandline (second try)
Date: Fri, 13 Apr 2001 01:30:00 -0000 [thread overview]
Message-ID: <200104130830.BAA28191@shell17.ba.best.com> (raw)
In-Reply-To: <87g0fd63n3.fsf@creche.redhat.com>
> The whole point is to preserve the arguments as-is.
...
> Since we're also the only ones talking I'm inferring that nobody else
> cares about drilling down on this subject any more. My future
> replies, if any, will be off-list unless somebody asks otherwise.
Before you disappear, let me just chime in from the peanut gallery that I
find the whole "crunch inferior arguments through sh" to be uncomfortable.
Can't we just have two command line routes, one that uses sh, and one that
does not (it would just execvp the arguments for the most part) ?
That way people who want "it works like the run command" get their option
and people who want "debug whatever I was running durnit" get theirs.
Todd Whitesel
toddpw @ best.com
next prev parent reply other threads:[~2001-04-13 1:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010330005457.A21793@llamedos.org>
2001-03-29 23:13 ` [PATCH] specify arguments to debugee from commandline Eli Zaretskii
2001-03-30 0:26 ` David Deephanphongs
2001-03-30 1:32 ` Eli Zaretskii
2001-03-30 3:00 ` Alexandre Oliva
2001-03-30 3:47 ` Pierre Muller
2001-03-30 8:01 ` David Deephanphongs
2001-03-30 12:37 ` Andrew Cagney
2001-03-30 5:06 ` Fernando Nasser
2001-03-30 5:20 ` Fernando Nasser
2001-03-30 13:28 ` [PATCH] specify arguments to debugee from commandline (second try) David Deephanphongs
2001-04-02 22:27 ` David Deephanphongs
2001-04-02 22:48 ` Alexandre Oliva
2001-04-05 21:27 ` Tom Tromey
2001-04-05 21:47 ` Alexandre Oliva
2001-04-05 21:21 ` Tom Tromey
2001-04-06 1:32 ` Eli Zaretskii
[not found] ` <87vgoi58lr.fsf@creche.redhat.com>
2001-04-06 9:26 ` Eli Zaretskii
2001-04-06 9:35 ` Pierre Muller
2001-04-06 11:00 ` Tom Tromey
2001-04-17 10:38 ` Andrew Cagney
2001-04-20 2:39 ` David Deephanphongs
2001-06-06 23:40 ` David Deephanphongs
2001-06-07 0:00 ` Eli Zaretskii
2001-04-06 11:03 ` Tom Tromey
2001-04-06 13:13 ` Eli Zaretskii
2001-04-10 22:27 ` David Deephanphongs
2001-04-11 1:55 ` Eli Zaretskii
2001-04-11 19:05 ` David Deephanphongs
2001-04-12 8:26 ` Tom Tromey
2001-04-12 14:13 ` David Deephanphongs
2001-04-12 17:21 ` Tom Tromey
2001-04-13 1:30 ` Todd Whitesel [this message]
2001-04-06 22:46 ` David Deephanphongs
2001-04-05 21:12 ` Tom Tromey
2001-04-06 1:36 ` Eli Zaretskii
2001-06-22 12:26 Deephanphongs, David
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=200104130830.BAA28191@shell17.ba.best.com \
--to=toddpw@best.com \
--cc=david@llamedos.org \
--cc=gdb-patches@sources.redhat.com \
--cc=tromey@redhat.com \
/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