Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@gnat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
	Eli Zaretskii <eliz@elta.co.il>,
	gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] Problem with '!' escaping with zsh/bash/ksh
Date: Wed, 21 May 2003 23:40:00 -0000	[thread overview]
Message-ID: <20030521234046.GH1027@gnat.com> (raw)
In-Reply-To: <3EB6BBAF.5080504@redhat.com>

Andrew,

On Mon, May 05, 2003 at 03:29:51PM -0400, Andrew Cagney wrote:
> Joel, testcase?
> 
> I was going to suggest gdb.base/args.exp but someone's already added that.
> Consider an addition to that existing test case pre-approved (and any 
> other evil combinations you come up with).

Coming back to this message, I am not sure I understand what you were
suggesting, do you remember? As far as I can tell, args.exp verifies
that all arguments are correctly passed to the inferior.

In our case, the '!' character was escaped in the executable name, but
not in the args (ie the args were left alone). So adding an extra test
for arguments containing '!' is fine, but not relevant to the issue at
hand.

At this point, I am considering the addition of a new test case, which
would basically:

  - compile args.c
  - copy args to bang!
  - gdb bang!
  - run

The problem is that this test should work fine on Unix machines
but I am guessing that this won't work so well on Windows boxes for
instance.

What do you think?

-- 
Joel


  parent reply	other threads:[~2003-05-21 23:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02 23:35 Joel Brobecker
2003-05-03  8:39 ` Eli Zaretskii
2003-05-03 14:34   ` Daniel Jacobowitz
2003-05-03 16:51     ` Joel Brobecker
2003-05-03 16:59       ` Daniel Jacobowitz
2003-05-05 19:29         ` Andrew Cagney
2003-05-08 18:11           ` Joel Brobecker
2003-05-21 23:40           ` Joel Brobecker [this message]
2003-05-22 17:50             ` Andrew Cagney
2003-05-24  7:40             ` Eli Zaretskii
2003-05-03 19:00       ` 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=20030521234046.GH1027@gnat.com \
    --to=brobecker@gnat.com \
    --cc=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=eliz@elta.co.il \
    --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