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 13:05:32 -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:
>./test.exe prints only 'parent:Test' - parent works as expected - and gives a
>test.exe.stackdump - after 30 seconds.
>
>
>an example gdb session looks like:
>attach <child pid>
>b load
>c (needs up to 30 seconds for return)
>n
>n
>n
>s (step into dll's cTest::get method)
>p t (print cTest::t, _M_p seems to be corrupt)
>$1 = {static npos = <optimized out>,
> _M_dataplus = {<std::allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<
>No data fields>}, <No data fields>}, _M_p = 0x0}}
>n
>Program received signal SIGSEGV, Segmentation fault.
>0x6c4b95be in cygstdc++-6!_ZNSsC1ERKSs () from /usr/bin/cygstdc++-6.dll
>
> Any idea to fix or circumvent this error
I don't get a coredump. What I do get, after a 30 second wait, is:
child:Test
Maybe a snapshot will work better for you: http://cygwin.com/snapshots/
--
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