From: Eli Zaretskii <eliz@delorie.com>
To: tromey@redhat.com
Cc: deephan@erols.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] specify arguments to debugee from commandline (second try)
Date: Fri, 06 Apr 2001 01:32:00 -0000 [thread overview]
Message-ID: <200104060832.EAA17613@indy.delorie.com> (raw)
In-Reply-To: <87n19uirbk.fsf@creche.redhat.com>
> 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.
next prev parent reply other threads:[~2001-04-06 1:32 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 [this message]
[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
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=200104060832.EAA17613@indy.delorie.com \
--to=eliz@delorie.com \
--cc=deephan@erols.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