This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: 1.7.9: static const std::string initialization lost in child process when using fork, dlopen
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 21 Aug 2011 12:50:01 -0400
- Subject: Re: 1.7.9: static const std::string initialization lost in child process when using fork, dlopen
- References: <1558100995.357508.1313927301638.JavaMail.fmail@mwmweb008>
- Reply-to: cygwin at cygwin dot com
On Sun, Aug 21, 2011 at 01:48:21PM +0200, whans@web.de wrote:
>Hello,
>??
>it seems that a child process does not see the initialization of a
>static const std::string variable if it is defined in a dll. Instead this corrupt variable
>lead to a STATUS_ACCESS_VIOLATION.
>??
>The following 4 example files demonstrate this behaviour:
Am I the only person who sees lots of strange characters in the examples
below where, presumably there is supposed to be whitespace?
cgf
>1) dllif.h: ?? ?? ??(define the dll's interface)
>#include <string>
>class cTestIf {
>public:
>?? virtual std::string get() = 0;
>};
>??
>??
...
--
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