This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Segmentation fault with ls command
- From: Larry Hall <cygwin-lh at cygwin dot com>
- To: Greg Rudd <G dot Rudd at isu dot usyd dot edu dot au>, Cygwin List <cygwin at cygwin dot com>, Didier Debuf <didier at mail dot usyd dot edu dot au>
- Date: Sun, 30 May 2004 13:41:52 -0400
- Subject: Re: Segmentation fault with ls command
- References: <BCDF9A83.FFF8%G.Rudd@isu.usyd.edu.au>
- Reply-to: Cygwin List <cygwin at cygwin dot com>
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:
<http://www.cygwin.com/ml/cygwin/2004-05/msg00839.html>
>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/