Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 21 Nov 2002 18:41:46 -0800 (PST) From: Matt X-Sender: To: Subject: Re: Want to release 1.3.16 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 17 Nov 2002, Matt wrote: > On Sat, 16 Nov 2002, Christopher Faylor wrote: > > > 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. > > Actually, I didn't know that -- thanks for the tip! :) > I'll attach in VC++ which should resolve the symbols in system DLLs > properly. The hang I was seeing appears to be eliminated by the recent changes to fix some other program's hangs. I figured the problem wasn't specific to nessusd. Thanks to Corinna and cgf for checking in fixes! -- http://www.clock.org/~matt -- 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/