Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-ID:	<779F20BCCE5AD31186A50008C75D99791716F3@SILLDN_MAIL1>
From:	"Fifer, Eric" <EFifer AT sanwaint DOT com>
To:	"'cygwin-developers AT sourceware DOT cygnus DOT com'"
	<cygwin-developers AT sourceware DOT cygnus DOT com>
Subject:	RE: problem with fork/exec in Cygwin DLL called from non-Cygwin E
	XE
Date:	Thu, 2 Mar 2000 18:26:00 -0000
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2448.0)

"Chris Faylor" writes:
>Since fork/exec are not aware of LoadLibrary calls, I am surprised that you
>would see any success anywhere.  dlopen() may work better.

I was using LoadLibrary in an attempt to emulate whatever
Excel is doing.  The real goal is to be able to use 
fork/exec/etc from Cygwin-capable DLLs called from Excel.

>It doesn't know about
>your use of LoadLibrary so it doesn't duplicate it.  Then, the code tries
to
>jump into func() which doesn't exist.

Hmm ...

Do you think adding a cygwin_record_dll() hook would be
too ugly?

Thanks.

Eric Fifer

- Raw text -