Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date:	Mon, 29 Dec 2003 22:41:28 -0500
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.5.6-pre: Occasional bad memory accesses within cygwin1.dll
Message-ID:	<20031230034128.GB20304@redhat.com>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<010b01c3cd5a$a138c9b0$d6e28351 AT starfruit>
Mime-Version:	1.0
In-Reply-To:	<010b01c3cd5a$a138c9b0$d6e28351@starfruit>
User-Agent:	Mutt/1.4.1i
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

On Sun, Dec 28, 2003 at 03:52:33PM -0000, Max Bowsher wrote:
>Less common failures include shell scripts receiving terminating with a
>"Hangup" message, or locking up entirely.
>
>Debugging suggestions welcome.

Forgot to add that the obvious thing to try here is attaching to the
process in the "locking up entirely" situation.

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