Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
MIME-Version:	1.0
Subject:	bug in dll_crt0_1()?
X-MimeOLE:	Produced By Microsoft Exchange V6.0.5762.3
content-class:	urn:content-classes:message
Date:	Fri, 24 May 2002 11:51:36 +1000
Message-ID:	<FC169E059D1A0442A04C40F86D9BA7600C6151@itdomain003.itdomain.net.au>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	<cygwin-developers AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id g4O1pds17735

Interesting situation:

I have a function that is called from dll_crt0_1 via
  do_global_ctors (&__CTOR_LIST__, 1);
that uses malloc(). Malloc is not ready until malloc_init, called from
heap_init() called from memory_init(), called from ... dll_crt0_1.

Should the memory_init() occur earlier, or should the global constructor
call memory_init() directly? or should malloc() check that memory_init()
has been called?

Rob

- Raw text -