Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Sun, 8 Apr 2001 19:55:33 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: G++ guru's please comment - Re: FW: pthread_create problem in Cygwin 1.1.8-2]
Message-ID:	<20010408195533.F19783@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<EA18B9FA0FE4194AA2B4CDB91F73C0EF08EEC2 AT itdomain002 DOT itdomain DOT net DOT au>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.11i
In-Reply-To:	<EA18B9FA0FE4194AA2B4CDB91F73C0EF08EEC2@itdomain002.itdomain.net.au>; from robert.collins@itdomain.com.au on Mon, Apr 09, 2001 at 09:38:57AM +1000

On Mon, Apr 09, 2001 at 09:38:57AM +1000, Robert Collins wrote:
>Background: pthread_create starts the new thread with a wrapper
>function. The wrapper function runs the thread function, and when the
>user function returns then cleans up the unix structures and calls
>ExitThread(0); The crash occurs _before_ control returns to the wrapper
>function. This implies it's a problem in the return code.

Ok.  Single step the assembly instructions and see if you can find
out where it is failing.  I still suspect a corrupt stack.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -