delorie.com/archives/browse.cgi | search |
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 |
Subject: | RE: G++ guru's please comment - Re: FW: pthread_create problem in Cygwin 1.1.8-2] |
MIME-Version: | 1.0 |
X-MimeOLE: | Produced By Microsoft Exchange V6.0.4417.0 |
content-class: | urn:content-classes:message |
Date: | Mon, 9 Apr 2001 11:13:53 +1000 |
Message-ID: | <EA18B9FA0FE4194AA2B4CDB91F73C0EF79B8@itdomain002.itdomain.net.au> |
Thread-Topic: | G++ guru's please comment - Re: FW: pthread_create problem in Cygwin 1.1.8-2] |
Thread-Index: | AcDAhmyVy51UsyQ6T0WSHLL8MfwLCgAASgAg |
From: | "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au> |
To: | <cygwin AT cygwin DOT com> |
X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id VAA11648 |
> -----Original Message----- > From: Christopher Faylor [mailto:cgf AT redhat DOT com] > Sent: Monday, April 09, 2001 9:56 AM > To: cygwin AT cygwin DOT com > Subject: Re: G++ guru's please comment - Re: FW: > pthread_create problem > in Cygwin 1.1.8-2] > > > 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 > I will, once I have a good binary to compare with. I don't know what return 0; in a try{} should look like. Just for fun I removed the printf, and the crash went away. It also never appears with only one thread running. I've had a quick read of the asembly and will report back. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |