Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 15 Nov 2000 00:49:19 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: make -j hangs? anyone else? Message-ID: <20001115004918.A27967@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20001115050649 DOT 13154 DOT qmail AT web117 DOT yahoomail DOT com> <4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20001114231557 DOT 00c7a990 AT pop DOT bresnanlink DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <4.3.2.7.0.20001114231557.00c7a990@pop.bresnanlink.net>; from cabbey@bresnanlink.net on Tue, Nov 14, 2000 at 11:17:16PM -0600 On Tue, Nov 14, 2000 at 11:17:16PM -0600, Chris Abbey wrote: >At 21:06 11/14/00 -0800, Earnie Boyd wrote: >>Chris has warned before not to use the job switches for make. > >hmm... not sure how I missed them. (well, ok the ~35 messages/day >on this list alone could be part of it.... ;) Thanks for the 'minder >Earnie. Actually, I think DJ warns of this sometimes. The problem is that Windows (or maybe just Cygwin) lacks the ability to track load average, so, in 1.1.4 and before you could end up running up to cygwin's pid table size processes. Since 1.1.5 uses NT's process limit that number grows by quite a bit. Something like 'make -j2' should work ok, though. I've just (2 minutes ago) uncovered a problem that was due to the fact that cygwin is now using win32 pids. In windows, when you are starting new processes that exit quickly, the pids can look like this 1234 5678 9012 1234 9012 5678 i.e., the pids repeat themselves. If this happens with something that is trying to keep track of pids, like bash it seems to lead to confusion. I don't know if make is the same way or not, though. The symptom in bash is, coincidentally, a "hang", although the bash process is accumulating CPU. I'll have to work around this somehow in cygwin. Anyway, I don't like the sound of your problem. It shouldn't hang the way that you are seeing it hang. If I can duplicate the problem, I'll see if I can fix it. But, then once I do fix it -- don't do that! :-) cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com