bug in dll_crt0_1()?

[Christopher Faylor]

On Fri, May 24, 2002 at 11:51:36AM +1000, Robert Collins wrote:
>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?

Adding malloc calls to cygwin's startup code is something that should
be given a lot of thought.  Ditto, adding ctors.  If you're profiling
cygwin, I think you'll find that a surprising amount of time is
taken up in ctors.

cgf