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
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Wed, 12 Mar 2003 11:13:47 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: "Willis, Matthew" <Matthew DOT Willis AT CIBC DOT ca>
cc: cygwin AT cygwin DOT com
Subject: RE: cygwin 1.3.20-1 - strange problems with long command lines in 
 nt4
In-Reply-To: <BC46D442BCFB6340A9BB1CED6766E36E024E7023@tons2226>
Message-ID: <Pine.GSO.4.44.0303121109340.13699-100000@slinky.cs.nyu.edu>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 12 Mar 2003, Willis, Matthew wrote:

> Igor wrote:
>
> >Matt,
> >
> >A virus checker *shouldn't* affect your command line length limit...
> >Try running the offending command under strace, e.g.,
> >
> >strace -o echo.strace /usr/bin/echo ${PATH}${PATH}
> >
> >and look at the tail of the output.  That should give you a clue of where
> >it's hanging.  If you're having a hard time reading the strace output, and
> >if the output is not too large, you could post it here so other people
> >could try to help you.
> >       Igor
>
> I did try an strace experiment... not very helpful I am afraid:
>
> WILLISMA AT toww5462 ~
> $ strace -o foo.txt echo.exe ${PATH} > /dev/null; wc foo.txt
>     408    4141   40604 foo.txt
>
> WILLISMA AT toww5462 ~
> $ strace -o foo.txt echo.exe ${PATH}${PATH} > /dev/null; wc foo.txt
>       0       0       0 foo.txt

You may be hitting the command-line limit with bash.  Try the above with
cmd.exe.  See below.

> Yesterday, in pre-rebase versions of cygwin I was able to get ls to hang;
> whilst hanging I could see stuff like I described in
>
> http://sources.redhat.com/ml/cygwin/2002-11/msg00371.html
>
> As of the latest rebase, I don't see hangs with ls.exe, I just get the
> immediately-return-to-command-line effect.
>
> Other observations:
>
> If I launch cmd.exe as the shell, and manually put c:\cygwin\usr\bin and
> c:\cygwin\bin on my path,
>
> c:\cygwin\bin\ls.exe *               -- works fine; but I wonder if ls is being passed "*" or a list of args

FYI, yes, it is...  cmd.exe doesn't do globbing.

> c:\cygwin\bin\echo.exe *             -- works fine
> c:\cygwin\bin\echo.exe %PATH%        -- works fine
> c:\cygwin\bin\echo.exe %PATH%%PATH%  -- fails, immediately returns to command line

Try stracing the last line above...
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
  -- /usr/games/fortune


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/