delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/1998/10/28/17:09:16

From: cgf AT cygnus DOT com (Christopher Faylor)
Subject: Re: Analysis of non-cygwin app loading cygwin DLL problem
28 Oct 1998 17:09:16 -0800 :
Message-ID: <19981028194240.A18414.cygnus.cygwin32.developers@cygnus.com>
References: <9810282342 DOT AA29302 AT modi DOT xraylith DOT wisc DOT edu>
Mime-Version: 1.0
To: Mumit Khan <khan AT xraylith DOT wisc DOT edu>, cygwin32-developers AT cygnus DOT com

On Wed, Oct 28, 1998 at 05:42:14PM -0600, Mumit Khan wrote:
>So, basically we need something similar to dll_crt0_1 that is called from
>dll_dllcrt0 to initialize the various state information in Cygwin when
>a Cygwin DLL is loaded for the first time by a non-cygwin app.

Don't you really want something similar to cygwin_crt0?  In the case
of a cygwin dll loaded via LoadLibrary all of the per_process information
is missing.  That would have to be provided via some other mechanism, possibly
via some code in init.cc which would detect if the dll was loaded via a
LoadLibrary or "normally".  In the LoadLibrary case, init.cc could actually
call dll_crt0 with its own per_process information.

Actually, maybe that's the way it should be anyway...

cgf

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019