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: Sun, 17 Nov 2002 10:08:11 -0800 (PST) From: Matt X-Sender: To: Subject: Re: Want to release 1.3.16 In-Reply-To: <20021116233019.GA10048@redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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. > 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. Er -- I didn't say it was a showstopper, I said that I'd like a few more days to look into it. If there are more urgent matters that would be resolved by a new release, that's fine too. Just thought I would chime in to the open question. Sorry if I missed something in the mailing list guidelines that I may have violated by doing so. nessus is an open source security scanner. http://www.nessus.org . I'll mail the list with by debugging progress on tuesday or so. -- http://www.clock.org/~matt