Re: Strange Cygwin issue

[David Abrahams <dave at boost-consulting dot com>]

Igor Pechtchanski <pechtcha@cs.nyu.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/