Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: Chris Faylor Date: Tue, 10 Oct 2000 17:16:36 -0400 To: cygwin AT sources DOT redhat DOT com Subject: Re: dllwrap and excluded symbols Message-ID: <20001010171636.A6206@cygnus.com> Reply-To: cygwin AT sources DOT redhat DOT com Mail-Followup-To: cygwin AT sources DOT redhat DOT com References: <200010102057 DOT QAA12754 AT envy DOT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: ; from timr@viaworks.com on Tue, Oct 10, 2000 at 02:06:49PM -0700 On Tue, Oct 10, 2000 at 02:06:49PM -0700, Tim Reed wrote: > >The problem I'm having is coming up in Windows 2000. I'm writing a dll >in C with the Cygwin tools. This dll is loaded by another dll compiled >with Visual Basic. My cygwin compiled dll needs to load things like crtdll >and the like. It does not use cygwin1.dll. It works fine in Win98 but >fails in Windows 2000. > >Using Taskinfo2000 and a debugger I've noticed that the dll just doesn't >load in the C runtime dlls in Win2k. Consequently, when that dll makes a >call to malloc I get a Memory Access Violation since the symbol wasn't >resolved to a valid address. > >Would you recommend that I write an entry point that just calls >LoadLibrary on the needed dlls? > >I realize you might not know the inner workings of mingw, but do you know >where I get this kind of info? http://www.mingw.org/ cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com