Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: cygwin@cygwin.com Subject: Re: Strange Cygwin issue References: From: David Abrahams Date: Mon, 19 May 2003 18:49:46 -0400 In-Reply-To: (Igor Pechtchanski's message of "Mon, 19 May 2003 17:22:18 -0400 (EDT)") Message-ID: 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 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/