Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Mon, 4 Feb 2002 10:00:02 -0500
From: Jettero Heller <cygwinuser AT voltar-confed DOT org>
To: cygwin AT cygwin DOT com
Subject: dll
Message-ID: <20020204100002.A19672@corky.voltar-confed.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i

I'm attempting to write a dll that gives some TCP support to
FoxPro.

FoxPro is pretty antiquated... it's been challenging. ;)


I got to a place where my dll loads up fine from a .exe, but
if foxpro tries to use it, it sagfaults:

VFP caused an invalid page fault in
module KERNEL32.DLL at 0167:bff7b9a6.

The line that causes the sagfault appeared to be a harmless
int sfd = socket() call.  *ponder*

I had done a few other cygwin1.dll calls (sprintf, strcpy,
and so on); and theorized that it had something to do with
the file handle.


I did a similar int fd = open() call.  It worked from my
.exe load of the .dll, but crashed with foxpro.



I believe the problem is that foxpro is linked against a
.dll that clashes with the cygwin1.dll ... or something
like that.


Any suggestions at all would be greatly appreciated.

-- 
If riding in an airplane is flying, then riding in a boat is swimming.
17 jumps from a c182.  Roughly 142 seconds of free fall.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/