From: Michael Snyder <msnyder@cygnus.com>
To: tromey@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: Inferior command line arguments
Date: Fri, 28 Sep 2001 11:24:00 -0000 [thread overview]
Message-ID: <3BB4C04D.22C3DAB5@cygnus.com> (raw)
In-Reply-To: <87zo7gq7gb.fsf@creche.redhat.com>
Tom Tromey wrote:
>
> Tonight I did some hacking to let one set the inferior command line
> arguments from the gdb command line. This feature has been discussed
> at length at least twice (most recently in March-April 2001 on
> gdb-patches). I would like to get some feedback on my general
> approach before I do the polishing.
>
> For the user the feature looks like this:
>
> gdb --args program arg1 arg2 ... argN
>
> Actually, --args can appear anywhere:
>
> gdb program --args arg1 arg2 ... argN
Without having read thru your patch, how are you able to distinguish
between args that are intended for GDB (such as "program" above), and
args that are intended for the inferior? You have "program" appearing
both before and after the "--args" flag. How are you picking it out
as special? How will you pick out other args that are intended for
GDB and not for the inferior, such as "-nw"?
next prev parent reply other threads:[~2001-09-28 11:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 21:02 Tom Tromey
2001-09-28 1:31 ` Eli Zaretskii
2001-09-28 5:26 ` Tom Tromey
2001-09-28 7:21 ` Eli Zaretskii
2001-09-28 7:50 ` Tom Tromey
2001-09-28 9:25 ` Eli Zaretskii
2001-09-30 12:07 ` Christopher Faylor
2001-10-01 0:39 ` Eli Zaretskii
2001-10-01 8:07 ` Tom Tromey
2001-10-01 8:10 ` Christopher Faylor
2001-09-28 11:24 ` Michael Snyder [this message]
2001-09-28 11:32 ` Tom Tromey
2001-09-28 11:59 ` Daniel Jacobowitz
2001-09-28 12:24 ` Tom Tromey
2001-09-29 2:23 ` Eli Zaretskii
2001-09-28 12:27 ` Andrew Cagney
2001-09-28 12:42 ` Daniel Jacobowitz
2001-09-28 14:19 ` Tom Tromey
2001-09-28 14:22 ` Daniel Jacobowitz
2001-09-29 1:23 ` David Deephanphongs
2001-10-01 8:09 ` Tom Tromey
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=3BB4C04D.22C3DAB5@cygnus.com \
--to=msnyder@cygnus.com \
--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