delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1998/08/21/02:58:16

From: hammersley AT austin DOT apc DOT slb DOT com (Richard Hammersley)
Subject: Command line length?
21 Aug 1998 02:58:16 -0700 :
Message-ID: <35DCACB6.265E98B1.cygnus.gnu-win32@austin.apc.slb.com>
Mime-Version: 1.0
To: gnu-win32 AT cygnus DOT com

Dear all,
I am a newbie to the great toolset shipped by cygnus. It
is proving v. useful to run my unix scripts on windows.
However, is there a problem with line lengths? My problem
script runs fine, until something like 1000 (17*80) chars is reached.
The command line is printed and appears to run and then

(C:\apps\Cygnus\B19\H-i386-cygwin32\bin\bash.exe 1010) Exception: STATUS_ACCESS_
VIOLATION
(C:\apps\Cygnus\B19\H-i386-cygwin32\bin\bash.exe 1010) Dumping stack trace to ba
sh.exe.core

if I truncate the line it works fine.

Did a search for command line length on the archives, but
found only references to use xargs.

Any suggestions/ideas,

Much thanks,
Richard
-- 
Richard Hammersley  Schlumberger Austin Product Center - Research
mailto:hammersl AT slb DOT com  voice:512 331 3731  fax:512 331 3760
8311 North RR 620, Austin, TX78726, USA
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019