Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <013001c2f2cd$d346df90$226b883e@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: "Mike W." <mw487 AT yahoo DOT com>, <cygwin AT cygwin DOT com>
References: <20030325043654 DOT 20391 DOT qmail AT web10009 DOT mail DOT yahoo DOT com>
Subject: Re: I can jam cygwin in 2 minutes - can you?- "Cannot fork: Permission denied" jam
Date: Tue, 25 Mar 2003 12:55:32 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Mike W. wrote:
> This relates to a bug in Win NT 2000 sp3 or cygwin-
> hard to say which.  I can only exercise the bug in
> cygwin, but I would like to exercise it from
> command.exe- see below.  Another user jammed cygwin in
> 183 iterations of the loop, after two days without a
> reboot.  I am not alone.
>
> This script, "crashme", will jam cygwin even faster
> than before- jam times are now down to about 2 minutes
> on my hardware! (less interaction with terminal- ha
> ha!)  Wow.  Otherwise, I can run all day unless I try
> to build some open source software.
>
> #! /bin/sh
> i=1  # 1 Infinite Loop
> /usr/bin/ps -al |grep PID
> while test $i != 0
> do
> /usr/bin/ps -al | grep ps   #PID value
> done
>
> (I have "grep" for Win NT and pslist (like ps, search
> for pstools in google), and I would like to run the
> above type script in command.exe.  Can anyone
> translate the above into something that will run
> within command.exe?  have pity...)
>
> Run the script in cygwin like this:
>
> ./crashme >r7.txt 2>&1
>
> and after you reboot ;-} or ^C you will have a nice
> record of the PIDs used preceding the jam or ^C.  I am
> trolling for similar problems on other peoples
> hardware, so here is some google bait:  (email me if
> you want the whole 151K file)
>
...
>
> Notice that the PID and WINPID do not always increase
> monotonically- but damn close.
...
>> This relates to a bug in my copy of cygwin, which
>> jams
>> when the PID goes over about 36800.  With a script,
>> this can easily happen in less than 10 minutes, like
>> during a build.
>>
>> How high can your PID go before you jam cygwin?  You
>> will have to reboot to use cygwin after jamming it.

OK, I tried this.

I killed it when I got bored, and crashme had produced a 1.3MB file
recording 18688 pids.

NOT EVEN ONE was greater than 4096.

Also, they did *not* increase monotonically at all. They looked mostly
random to me.

WinXPSP1, Cygwin 1.3.22, mostly up-to-date.

Max.


--
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/