Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 3 Dec 2001 13:27:51 -0500 From: Ashok Vadekar To: cygwin AT cygwin DOT com Subject: Shell meta character expansion problems Message-ID: <20011203132751.C12119@volta.certicom.com> Reply-To: avadekar AT certicom DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i I recently updated my visual C installation, and for paranoia reasons I maintained the original install (neither uses the registry, they are just directory trees for command-line use). I happened to put the new tree a little "deeper" that the original install, and noticed that I can't grep through the header files with an absolute path. The following fails: grep your_symbol_here /d/sdks/vc5sp5/vc98/includes/* but grep your_symbol_here /d/sdks/vc5sp5/vc98/includes/*.h works. Also, this fails ls /d/sdks/vc5sp5/vc98/includes/* I figured out that ls ./sdks/vc5sp5/vc98/includes/* filed, but ls ./vc5sp5/vc98/includes/* worked (from the obvious, appropriate cwd's). The source to grep turned up nothing, but then I looked at the shell (bash). It appears that expandmeta() in expand.c (line 1124) has a lower limit for expanded output of 16K, otherwise a size computed from PATH_MAX. I can't really tell if the failure I have is due to this computed size, since the allocated buffer gets passed into expmeta() as an un-sized char *. However, based on what I see at the command line, it certainly seems that the wildcard expansion is running out of memory. Is there anyone familiar enough with this to shove me in the right direction? -- 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/