Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Fri, 29 Sep 2000 16:40:54 -0700 (PDT)
From: Tim Reed <timr AT viaworks DOT com>
To: cygwin AT sources DOT redhat DOT com
Subject: Re: dll loading in Win2k
In-Reply-To: <Pine.LNX.4.10.10009281030420.25101-100000@vserver.viaworks.com>
Message-ID: <Pine.LNX.4.10.10009291640210.6011-100000@vserver.viaworks.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



I guess this one has everyone stumped?



On Thu, 28 Sep 2000, Tim Reed wrote:

> 
> I'm writing a COM add-in for MS Outlook in Visual Basic. This VB code will
> load in .dll compiled with the latest cygwin tools with the -mno-cygwin
> option. This cygwin dll is written in C, compiled with gcc and made a dll
> by dllwrap.
> 
> When I build my app and run it in Win98 all is well. Outlook loads my COM
> add-in at startup, and the COM add-in loads my mingw dll upon the first
> invokation of a function in the dll. Consequently, the first invokation of
> a function from that dll will also load in all the dll's it needs to run
> like crtdll.dll, wsock32.dll, gmp202.dll and more. 
> 
> Clearly there is some mechanism in that allows code generated by dllwrap
> to automatically load dll's that its target depends on.
> 
> When I build and run this app in Windows 2000 the dll made by dllwrap
> fails to load the dll's it depends on. Naturally, the first call to
> something like malloc causes a memory access exception and kills the app.
> If fact, it happens to be a call to malloc that kills the app.
> 
> I've made executeables in Win2k that use the same set of native windows
> dll's like crtdll.dll, wsock32.dll, etc except the dll that I made. Those
> executeables work fine. The problem seems to be my dll's code to
> implicitly load other native windows dll's.
> 
> 
> Does anyone know how the implicit loading of dll's in Win2k could fail to
> work?
> 
> 
> 
> Tim Reed
> 
> 
> 


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com