On 11/7/2014 4:11 AM, Corinna Vinschen wrote:
>
> - GCC 4.9.2-1 DLLs accidentally call __cxa_atexit with the wrong DSO
> handle value. This Cygwin update allows this scenario throughout.
> It now understands *any* DSO handle value, as long as it's a pointer
> into the DSO's address space.
> This fixes: https://cygwin.com/ml/cygwin/2014-11/msg00122.html
>
> If you don't build applications or DLLs with Cygwin, you can safely
> ignore this change.
>
>
> If you want to help testing this new release (which I seriously hope
> for), you can find it in your setup-x86.exe or setup-x86_64.exe as
> "test" release.
>
>
>
I take it from now on it should be OK to take the default for
__cxa_atexit
when configuring to build gcc. Thanks for explanation.
I'm repeating some tests with 1.7.33-0.8 and gcc/gfortran 4.9.2-1
no surprises, thanks (following segfault apparently unchanged, running with AV
and Defender disabled, but failure not seen with gfortran 5.0):
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
1181925 [main] profile_omp 3684 fixup_mmaps_after_fork: ReadProcessMemory failed
for MAP_PRIVATE address 0x6FE5FC60000, Win32 error 998
2248013 [main] profile_omp 3684 C:\users\tim\tim\tim\src\campbell\Profile_send_3
Nov14\profile_omp.exe: *** fatal error in forked process - recreate_mmaps_after_
fork_failed
3891395 [main] profile_omp 3684 cygwin_exception::open_stackdumpfile: Dumping st
ack trace to profile_omp.exe.stackdump
6 [main] profile_omp 1992 fork: child -1 - forked process 3684 died unexpe
ctedly, retry 0, exit code 0x100, errno 11
11849 [main] profile_omp 1992 cygwin_exception::open_stackdumpfile: Dumping st
ack trace to profile_omp.exe.stackdump
--
Tim Prince
--
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
