Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: Strange Cygwin issue
References: <Pine DOT GSO DOT 4 DOT 44 DOT 0305191717450 DOT 26639-100000 AT slinky DOT cs DOT nyu DOT edu>
From: David Abrahams <dave AT boost-consulting DOT com>
Date: Mon, 19 May 2003 18:49:46 -0400
In-Reply-To: <Pine.GSO.4.44.0305191717450.26639-100000@slinky.cs.nyu.edu> (Igor
 Pechtchanski's message of "Mon, 19 May 2003 17:22:18 -0400 (EDT)")
Message-ID: <uhe7qh7qt.fsf@boost-consulting.com>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3.50 (windows-nt)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu> writes:

>
> Dave,
>
> Have you tried compiling a small DOS program with bcc and seeing what it
> would interpret its parameters as?  It might be helpful if it printed one
> argument per line, or somehow indicated where the break in the arguments
> happens.

I did precisely that (unless a DOS program is different from a Win32
command-line program, in which case I don't know how to do it).  I
quote:

    >> shell seems to be a fine way to experiment with it.  the weird thing
    >> is, I built a little windows app win MSVC to print out all of
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    >> its argv, and if I invoke it like this:
       ^^^^^^^^
    >>
    >>       args "c:\foo-bar\baz"
    >>
    >> from either windows or cygwin, I see the same thing:
    >>
    >>      c:\foo-bar\baz
    >>

> Also, IIRC from my DOS hacking days, assembly programs received the whole
> parameter string at once, and had to parse it themselves, so it's possible
> that you have found a bug in TLIB's argument parsing routine.

Oh, that seems very likely... except that I'm sending it the same
string from Cygwin and NT AFAICT.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/