From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6231 invoked by alias); 3 Mar 2010 17:35:32 -0000 Received: (qmail 6210 invoked by uid 22791); 3 Mar 2010 17:35:30 -0000 X-SWARE-Spam-Status: No, hits=3.0 required=5.0 tests=AWL,BAYES_05,BOTNET X-Spam-Check-By: sourceware.org Received: from vms173005pub.verizon.net (HELO vms173005pub.verizon.net) (206.46.173.5) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 03 Mar 2010 17:35:26 +0000 Received: from [10.10.1.168] ([unknown] [209.190.166.162]) by vms173005.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0KYP009BEVIIPIU0@vms173005.mailsrvcs.net> for gcc-help@gcc.gnu.org; Wed, 03 Mar 2010 11:35:07 -0600 (CST) Message-id: <4B8E9DCA.7080808@verizon.net> Date: Wed, 03 Mar 2010 17:35:00 -0000 From: "John S. Fine" User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-version: 1.0 To: Anna Sidera Cc: gcc-help@gcc.gnu.org Subject: Re: cannot run many programs simultaneously References: In-reply-to: Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2010-03/txt/msg00046.txt.bz2 As Ian already explained, you're asking in the wrong place, because there is no reason to believe this is a GCC issue. The programming or linux-general forums at LQ would be a better place if this discussion needs a lot of follow up. http://www.linuxquestions.org/questions/ But for now, I'll give the basic answer: Anna Sidera wrote: > They run for some time and then they stop. However when I run only 3 of them simultaneously, and then run the other 3, they all finish successfully. > The obvious explanation for that behavior would be you hit either the system over commit limit or actual exhaustion of memory. Until you rule that out, you shouldn't look for any more obscure theory. Either one of those (over commit limit or exhaustion of memory) could be dealt with by increasing the amount of swap space in the system. If you lack enough physical memory to run 6 of those processes at once, increasing swap space would stop that from crashing, but might just make them crawl instead of crash. (Depending on what you mean by "stop", that might already be what you are experiencing. You may need to explain "stop" better in order to get a better answer). > I do not know if it is a bug or a problem with the memory the system allows me to use. The output of the ulimit -a command is the following: That isn't relevant. No matter what ulimit allows each process to use, it can't allow the total of all six processes to use more than is available for the whole system.