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:	Sat, 6 Jul 2002 00:24:08 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: g++ global constructor bug?
Message-ID:	<20020706042408.GA20252@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<200207052009 DOT g65K9Fr00451 AT new-york DOT lcs DOT mit DOT edu> <20020705203014 DOT GA18639 AT redhat DOT com>
Mime-Version:	1.0
In-Reply-To:	<20020705203014.GA18639@redhat.com>
User-Agent:	Mutt/1.3.23.1i

On Fri, Jul 05, 2002 at 04:30:14PM -0400, Christopher Faylor wrote:
>On Fri, Jul 05, 2002 at 04:09:15PM -0400, Douglas S. J. De Couto wrote:
>>the following program doesn't work right with cygwin, it seems the
>>global object sh constructor is not being called.
>
>If I had to guess I'd say that the constructor is kicked off before
>stdio is completely set up.

...and my guess would be wrong.  Constructors get kicked off first thing
in main.  That's plenty late enough in the process.  However, the
constructor list is empty in this case so nothing actually happens.

Looks like this is a variation of the binutils bug that was mentioned
earlier.  Does this go away if you revert to the binutils-20011002-1
release?

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -