Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Sat, 16 Nov 2002 14:59:58 -0800 (PST)
From: Matt <matt AT use DOT net>
X-Sender:  <matt AT cesium DOT clock DOT org>
To: <cygwin-developers AT cygwin DOT com>
Subject: Re: Want to release 1.3.16
In-Reply-To: <20021115220145.GA27950@redhat.com>
Message-ID: <Pine.NEB.4.30.0211161455380.12738-100000@cesium.clock.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 15 Nov 2002, Christopher Faylor wrote:

> Should I wait for more ntsec stuff or is it ok to release 1.3.16?
> There are a couple of problems I'd like to get resolved in a new
> release.

I'd like another few days to investigate a hang I'm seeing when running
nessus under cygwin. The nessusd and all of it's children hang in
libkernel32  somewhere in iname. The culprit that appears to cause the
hang is a socket accept() call in the parent process.

I'm trying to come up with a smaller reproducible test case. I can only
assume this would affect other programs -- the code in nessusd is nothing
particularly exotic.

Jus to make sure nessusd wasn't corrupting memory, I ran it on linux under
valgrind. valgrind reported no problems other than a few mionor
non-incremental leaks.

In any event, I'll send another mail when I have things more nailed down.


--
http://www.clock.org/~matt