Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: David Deephanphongs <deephan@telocity.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] specify arguments to debugee from commandline (second try)
Date: Thu, 07 Jun 2001 00:00:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1010607094727.28343O@is> (raw)
In-Reply-To: <20010607024045.A25325@llamedos.org>

On Thu, 7 Jun 2001, David Deephanphongs wrote:

> GDB will escape the following characters within an inferior argument:
> ^|&#<>\"'`$*?[](); \{}
>                   ^----space

The function which implements this should be OS-dependent.  What you 
wrote might work for /bin/sh, but not for non-Posix systems such as 
MS-Windows.

To avoid ugly OS-specific #ifdef's, perhaps we should add a hook function 
pointer whcih a port could set to point to its private function.  Then 
the code you wrote could be the default.

> One thing I'm a little confused about - I thought that GNU getopt
> (and getopt_long_only) moved arguments to the beginning of argv,
> but that doesn't seem to be the case.

This is controlled by the first character of the third argument to 
`getopt' and `getopt_long_only': if that first character is `-' or `+', 
`getopt' behaves differently as to the ordering of the options.  See the 
comments in getopt.c about the "enum ordering" type.


  reply	other threads:[~2001-06-07  0:00 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
     [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 [this message]
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=Pine.SUN.3.91.1010607094727.28343O@is \
    --to=eliz@is.elta.co.il \
    --cc=deephan@telocity.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