On Feb 20 10:38, Christopher Faylor wrote:
> 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.Indeed. But http://cygwin.com/acronyms/#PTC still applies, if this is possible at all with Visual Studio DLLs, I think. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
pgpfFQNN8tXsO.pgp
Description: PGP signature
