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 Reply-To: Cygwin List Message-Id: <6.1.0.6.0.20040530134037.0326db30@pop.theworld.com> X-Sender: Date: Sun, 30 May 2004 13:41:52 -0400 To: Greg Rudd , Cygwin List , Didier Debuf From: Larry Hall Subject: Re: Segmentation fault with ls command In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 12:04 AM 5/30/2004, you wrote: >Hi all > >When I try to do an ls * with a directory with 5793 file in it We seem to >get a error message saying >6 [main] -bash 644 cmalloc: cmalloc returned NULL >Segmentation fault Did you google? Here's a relevant thread from as recently as Tuesday: >In Tru64 ( the OS that I am most familiar with ) also gets a similar message >arg list too long in 4.0x. After talking with one of the OS development team >on another mailing list says that there is a limit that is imposed by the >posix standard But in 5.1.x there is a kernel parameter called >exec_disable_arg_limit in the proc section that enables a process to accept >an unlimited number of args. Does Caging have a similar feature where by >the maximum number of args that can be passed to a process can be changed. I don't know. What's Caging and what relevance does it have to Cygwin? -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/