Date: Mon, 24 Apr 2006 17:12:04 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Call for testing Cygwin snapshot
Message-ID: <20060424211203.GB23359@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20060424135339 DOT fb30e530d17747c2b054d625b8945d88 DOT c9e16a5122 DOT wbe AT email DOT secureserver DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060424135339.fb30e530d17747c2b054d625b8945d88.c9e16a5122.wbe@email.secureserver.net>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Mon, Apr 24, 2006 at 01:53:39PM -0700, Jerry D. Hedden wrote:
>Corinna Vinschen wrote:
>>It's time again to release a new Cygwin version.
>>
>>We're on the way to 1.5.20, and we're hoping that this release solves
>>or at least workarounds a couple of problems introduced in earlier
>>versions.  Please report back in this thread when you encounter a
>>problem, which you can't reproduce with 1.5.18 or 1.5.19.  We're
>>interested in regressions in the first place.
>>
>>Keep in mind that we can easier find problems if you attach a brief,
>>concise, selfcontained testcase, if possible in plain C, which allows
>>easy reproducing.
>
>Seems to have created some new ones.  I have a cron job (a bash script)
>that runs every 6 minutes, polling and downloading info off the web. 
>With the 2006-03-09 snapshot, it works fine.  However, I have
>experienced problems with most snapshots after it, including this one -
>the full 2006-04-24 16:48 GMT snapshot.  I have always had to revert
>back to 2006-03-09.
>
>The problem is the script hangs at various places and the stuck
>processes keep building up:
>> ps -a
>      PID    PPID    PGID     WINPID  TTY  UID    STIME COMMAND
>    26264       1   26264      26264  con 78809 15:39:13 /usr/bin/rxvt
>      368   26264     368       2252    0 78809 15:39:13 /usr/bin/bash
>    28904       1   28904      28904    ?   18 15:39:15
>/usr/bin/cygrunsrv
>     2020   28904    2020       1972    ?   18 15:39:15
>/usr/sbin/cygserver
>     2716       1    2716       2716    ?   18 15:39:17
>/usr/bin/cygrunsrv
>     2600    2716    2716      27672    ?   18 15:39:17 /usr/sbin/cron
>     1720       1   45204      37852    ? 78809 16:24:02 /usr/bin/diff
>    43456       1   37736      37680    ? 78809 16:30:02 /usr/bin/diff
>    43252       1   36456      43616    ? 78809 16:36:02 /usr/bin/mv
>    39364       1   22988       1628    ? 78809 16:42:02 /usr/bin/date
>    33100     368   33100      33496    0 78809 16:46:32 /usr/bin/ps
>
>The diff, mv and date processes above are examples of hung scripts. 
>Further, I have to kill these processes using the task monitor:  kill
>reports 'No such process'.

As mentioned above, a test case showing the problem sure would be nifty.
Also, knowing the first snapshot which shows the problem would be helpful.

cgf

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