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

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

On Wed, 28 Oct 1998, Christopher Faylor wrote:

> 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...
> 

Actually, the problem happens for both LoadLibrary or "normally", as long
as it's loaded from/by a non-cygwin app.

Just sent a patch to cygwin32-developers list ... could you please
comment when you see it? Our messages unfortunately crossed each other.

I really would like to see this solved for b20 if at all possible ...

Regards,
Mumit


- Raw text -


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