X-Spam-Check-By: sourceware.org
Date: Thu, 20 Jul 2006 15:30:27 -0400
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: 1.5.20: Occasional crash at address 0x6100365f (cygthread::stub() in cygthre
Message-ID: <20060720193027.GA14980@trixie.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <BAY105-F23A5F627708EC6C2DABF87B7600@phx.gbl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BAY105-F23A5F627708EC6C2DABF87B7600@phx.gbl>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Wed, Jul 19, 2006 at 05:30:05PM +1000, Kiyo Kelvin Lee wrote:
>Actually, I have 2 systems (one XP [AMD Athlon 64 3500] and one Win2K 
>[Celeron 900]) both have the same problem and attached are the cygcheck 
>output.
>
>My sh.exe is bash.exe.
>
>The crashes happen just sparsely and not upon all processes termination. 
>When I ran, say, configure for openbox-2, I always got at least a few 
>crashes but the configure procedure should have already ran hundreds of 
>processes. Note the crashes did not seem to affect the configure procedure 
>and configure finished just normally.
>
>I tried to debug bash and get the stack trace with no success.
>The crashing dialog is like attached to a ghost process. Click on CANCEL  
>does not start msdev.exe as the debugger.

Running msdev wouldn't be very interesting anyway.

Possibly setting CYGWIN=error_start=c:/cygwin/bin/gdb.exe might cause
gdb to pop up, however.

>Also tried to attach to a bash using gdb before running configure, the 
>crashes still happen but gdb just couldn't catch anything, the bash just 
>kept running (inside gdb).

I'm not sure what this means.  If bash kept running then that would
indicate that it isn't the bash which is crashing.  Possibly a forked

cgf
copy is crashing.

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

