Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Sat, 16 Nov 2002 18:30:19 -0500 From: Christopher Faylor To: Matt Cc: cygwin-developers AT cygwin DOT com Subject: Re: Want to release 1.3.16 Message-ID: <20021116233019.GA10048@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: Matt , cygwin-developers AT cygwin DOT com References: <20021115220145 DOT GA27950 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i On Sat, Nov 16, 2002 at 02:59:58PM -0800, Matt wrote: >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. 'iname' is just a generic name for an unknown location, isn't it? You never get useful symbol information from the system DLLs. I have no idea what nessus is or why this would be considered a show stopper. AFAIK there hasn't been any new networking changes since 1.3.15. cgf