X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=eS0zPImyP9hro5+Q/GCCgSuq0IvsU8AyHpqHAr2F+Qdkaz21JaVKG
	ia7qRuO3YvxWPLYdZ9YIx45o1UqPD5u8tpRoUpF8Z+dyFYAz9Ukduy6m8sQcnGdv
	jo5AHKg3gbWSRtw/1h8yViD4+uDrE0uS0wHhZvxcsAn9tbJ0/sFKmE=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=p5zA23OYzFJckk33ctdfsjDa9vM=; b=x/PHPrq/Cht0vBcMITCzMnQ0OVlv
	ejKExLUoLqREoAAksADhilUpNE1/IyUCqJWRD28hePmg6RaHAOJK6lPlYhjRrTxg
	2/RwzsnWHF6js2YdDYJ2oc+U5bOE3pSoL0+4FW+D3+VV/T2cJXa26DkIsOgCisg/
	aFc6O0fCTUwga4Y=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	mho-01-ewr.mailhop.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX1+0EaEzDaMMcowuu8d9z3k9
Date:	Thu, 20 Feb 2014 10:38:54 -0500
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Bug with dlopen() and fork()
Message-ID:	<20140220153854.GC7958@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CAMzR4E7ngKr5HN=QEZXLUuy0VxGbD_xDN7UaTKPmfbmmD8Bz0A AT mail DOT gmail DOT com> <CAMzR4E6eO=m_s4+js=AA_EGntU=LRj9ZURmUqrwYqdVJ31hQWw AT mail DOT gmail DOT com> <20140220145727 DOT GN2246 AT calimero DOT vinschen DOT de>
MIME-Version:	1.0
In-Reply-To:	<20140220145727.GN2246@calimero.vinschen.de>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Thu, Feb 20, 2014 at 03:57:27PM +0100, Corinna Vinschen wrote:
>On Feb 20 14:16, Jaime Fabregas Fernandez wrote:
>> Hello Corinna,
>> 
>> As you've checked, this behaviour doesn't appear with dll's created by
>> gcc, but it does with Visual Studio C++.
>> That minimal example compiled with VS will result in the freeze of the
>> child process.
>> 
>> ================ testlib.h ======================
>> #ifdef TESTLIB_EXPORTS
>> #define TEST_API extern "C" __declspec(dllexport)
>> #else
>> #define TEST_API extern "C" __declspec(dllimport)
>> #endif
>> 
>> TEST_API  int  mylib_open (const char *foo);
>> =============================================
>> 
>> =============== testlib.cpp ======================
>> #include "stdafx.h"
>> #include "testLib.h"
>> 
>>   int
>>   mylib_open (const char *foo)
>>   {
>>     return 1;
>>   }
>> ==============================================
>> 
>> I've tested several compiler and linker options with same result.
>> 
>> Any ideas?
>
>Using MS DLLs across fork in this way is unsupported.  If you get it
>working, you're just lucky.

Too bad.  We >just< missed the Thursday window.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -