X-Spam-Check-By: sourceware.org Date: Wed, 7 Dec 2005 10:45:17 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: octave-forge dependency? Message-ID: <20051207154517.GA32048@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <20051206214756.94651.qmail@web51510.mail.yahoo.com> <20051207152257.GB21747@calimero.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051207152257.GB21747@calimero.vinschen.de> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Wed, Dec 07, 2005 at 04:22:57PM +0100, Corinna Vinschen wrote: >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? It would be interesting to find out where this fails. There are other snapshots between 12-04 and 11-30. Does it also fail with those? cgf -- 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/