X-Spam-Check-By:	sourceware.org
Date:	Wed, 7 Dec 2005 16:22:57 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: octave-forge dependency?
Message-ID:	<20051207152257.GB21747@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20051206214756 DOT 94651 DOT qmail AT web51510 DOT mail DOT yahoo DOT com>
Mime-Version:	1.0
In-Reply-To:	<20051206214756.94651.qmail@web51510.mail.yahoo.com>
User-Agent:	Mutt/1.4.2i
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Dec  6 13:47, James R. Phillips wrote:
> FWIW, the 12-04 and 12-05 cygwin1.dll snapshots seem to cause
> octave-2.1.72-1 to hang on exit, but only if some significant
> computations and plots are done.  Just starting and then exiting
> doesn't trigger the problem.  This is a regression relative to the
> 11-30 snapshot.

That's fine, but you remember vaguely what I wrote in my call for
testing, right?  If you want the hang to persist in the next Cygwin
version, just don't give us any more information.  What about basic
debugging, strace, gdb, cygcheck output, ... a simple testcase?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat, Inc.

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

- Raw text -