Delivered-To:	listarch-cygwin AT sourceware DOT cygnus DOT com
Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id:	<199902171844.MAA26240@modi.xraylith.wisc.edu>
X-Authentication-Warning:	modi.xraylith.wisc.edu: localhost.xraylith.wisc.edu [127.0.0.1] didn't use HELO protocol
To:	"S. Krishnaprasad" <s DOT krishnaprasad AT tatainfotech DOT com>
cc:	"cygwin" <cygwin AT sourceware DOT cygnus DOT com>
Subject:	Re: DLL Not working
In-reply-to:	Your message of "Wed, 17 Feb 1999 11:31:27 +0530."
	<000a01be5a3a$f58994b0$11247aa3 AT sdf5_l1117 DOT tatainfotech DOT co DOT in>
Date:	Wed, 17 Feb 1999 12:44:45 -0600
From:	Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

"S. Krishnaprasad" <s DOT krishnaprasad AT tatainfotech DOT com> writes:
> Hi Mumit,
> 
> I downloaded the gmp port files from your ftp site and
> used the DLL in an application developed in Visual C++ 6.0
> on Windows NT 4.0 SP3.
> 
> When I run the application it gives me an error saying
> 
> The instruction at "0x77f6cc66" referenced memory at "0x00000010". The
> memory

The port on my ftp site is for cygwin B20, and I didn't test it at all
with MSVC application. I believe that I have to build the DLL with a
different entry point for MSVC apps to load gmp DLL correctly. Since
you're using MSVC, you might as well just build gmp with MSVC and avoid
all this.

BTW, bug reports without a test case, ie., ones that just say "I have a
problem", goes to the bottom of my *very long* problem/bug list and 
chances are I'll never get to it. 

Regards,
Mumit


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

- Raw text -