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: tromey at redhat dot com
- Subject: Re: [PATCH] specify arguments to debugee from commandline (second try)
- From: Eli Zaretskii <eliz at delorie dot com>
- Date: Fri, 6 Apr 2001 04:32:34 -0400 (EDT)
- 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> <87n19uirbk.fsf@creche.redhat.com>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> From: Tom Tromey <tromey@redhat.com>
> Date: 05 Apr 2001 22:29:35 -0600
>
> I'd like to modify gcc so I can invoke: `gcj --debug jc1 ...' and have
> gcc automatically insert `gdb --run' before the jc1 invocation. Then
> gdb will come up with the arguments magically set.
>
> 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.
Wouldn't such use get you in trouble in some cases anyway? The
arguments you put after "gdb --run" are evaluated by the shell, so
what GDB sees is not exactly what you typed. I'd imagine that in some
cases this would produce subtle differences between "gdb --run" and
issuing the `run' command inside GDB.