This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH] specify arguments to debugee from commandline (second try)
- To: Eli Zaretskii <eliz at is dot elta dot co dot il>
- Subject: Re: [PATCH] specify arguments to debugee from commandline (second try)
- From: Tom Tromey <tromey at redhat dot com>
- Date: 06 Apr 2001 09:52:16 -0600
- Cc: deephan at erols dot com, gdb-patches at sources dot redhat dot com
- References: <20010330005457.A21793@llamedos.org> <20010330163603.A27435@llamedos.org> <20010403013600.B7630@llamedos.org> <email@example.com> <200104060832.EAA17613@indy.delorie.com>
- Reply-To: tromey at redhat dot com
>>>>> "Eli" == Eli Zaretskii <firstname.lastname@example.org> writes:
>> Likewise I'd like to be able to simply insert `gdb --run' into shell
>> scripts or any other program-launching code to get the debugger to do
>> the tedious work for me.
Eli> Wouldn't such use get you in trouble in some cases anyway? The
Eli> arguments you put after "gdb --run" are evaluated by the shell,
Eli> so what GDB sees is not exactly what you typed. I'd imagine that
Eli> in some cases this would produce subtle differences between "gdb
Eli> --run" and issuing the `run' command inside GDB.
I don't understand. Can you give an example?
Maybe you mean that redirections won't work as expected. That's true.
I agree that is something that should be addressed.