This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [PATCH] specify arguments to debugee from commandline (second try)
- To: deephan at erols dot com
- Subject: Re: [PATCH] specify arguments to debugee from commandline (second try)
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 03 Apr 2001 02:48:27 -0300
- Cc: gdb-patches at sources dot redhat dot com
- Organization: GCC Team, Red Hat
- References: <20010330005457.A21793@llamedos.org><20010330163603.A27435@llamedos.org><20010403013600.B7630@llamedos.org>
On Apr 3, 2001, David Deephanphongs <deephan@erols.com> wrote:
> At this point, 99.5% of the work is done towards any of these options.
> My personal preference is towards 1) or 4).
Speaking as someone who isn't officially involved in the
decision-making of GDB, I'm leaning towards 3. --run (that I had
suggested originally) may imply gdb will actually start the program,
instead of just setting up the argument list. `--' is better in this
sense. I don't see much need of --args-enable; one can always use
./-- instead of -- if their core file is named --.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me