Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: deephan@erols.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] specify arguments to debugee from commandline
Date: Fri, 30 Mar 2001 03:00:00 -0000	[thread overview]
Message-ID: <orhf0b7daw.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20010330033426.A22133@llamedos.org>

On Mar 30, 2001, David Deephanphongs <deephan@erols.com> wrote:

> 2) There was a suggestion to change the syntax:
> 	you would be able to run gdb like so:
> 	gdb <various options>  -run <progname> [<arg1>...<argn>]

> My implementation is cleaner (it modiifies inferior_arguments directly)
> and keeps the GDB syntax exactly the same as it is now.

But it requires pre-parsing and quoting of the argument list, so you
can't just do something like:

gdb_foo () {
  gdb [options] -run foo ${1+"$@"}
}

and get the same argument list, if they contain blanks or equivalent.
I'd much rather see something that accepts an argument list, instead
of a single string containing multiple arguments that has to be
re-parsed by gdb.

-- 
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


  parent reply	other threads:[~2001-03-30  3:00 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010330005457.A21793@llamedos.org>
2001-03-29 23:13 ` Eli Zaretskii
2001-03-30  0:26   ` David Deephanphongs
2001-03-30  1:32     ` Eli Zaretskii
2001-03-30  3:00     ` Alexandre Oliva [this message]
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
     [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

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=orhf0b7daw.fsf@guarana.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=deephan@erols.com \
    --cc=gdb-patches@sources.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