Hello! Last days I've been trying to compile my application (synfig) using the both mingw and mingw-w64-i686 toolchains. In all cases the resulting binary refuses to run, raising segfault.
Few months ago (in May-June 2013) I was able to build and run the same binaries without any problems (on mingw only, mingw-w64-i686 wasn't tested by that time). After some investigation I have noticed that the gcc was updated since then to the version 4.7.3 (see http://cygwin.com/ml/cygwin-announce/2013-07/msg00019.html and http://cygwin.com/ml/cygwin-announce/2013-07/msg00011.html). I suspect that the mingw* packages, provided by cygports project should be rebuild against the new gcc to work correctly. Symptoms: * gtk-demo.exe from gtk cygport (mingw-w64-i686 toolchain) refuses to run - segfault * my application uses libboost and segfault comes from libboost_program_options-mt.dll (inspected with gdb). Then I have recompiled libbost myself (using the cygport file from your repository) and recompiled everything again. After that it still segfaults, but in other place. Inspecting with gdb doesn't give anything useful for me: ====== log start ====== $ gdb /usr/i686-w64-mingw32/sys-root/mingw/bin/synfig.exe <...snip...> Reading symbols from /usr/i686-w64-mingw32/sys-root/mingw/bin/synfig.exe...done. (gdb) run Starting program: /usr/i686-w64-mingw32/sys-root/mingw/bin/synfig.exe [New Thread 300.0x6a4] Program received signal SIGSEGV, Segmentation fault. 0x77c36fa3 in msvcrt!memcpy () from /cygdrive/c/WINDOWS/system32/msvcrt.dll (gdb) backtrace #0 0x77c36fa3 in msvcrt!memcpy () from /cygdrive/c/WINDOWS/system32/msvcrt.dll #1 0x6fc8ddd3 in libstdc++-6!_ZNSs12_S_constructIPKcEEPcT_S3_RKSaIcESt20forward_iterator_tag () from /usr/i686-w64-mingw32/sys-root/mingw/bin/libstdc++-6.dll #2 0x00ff002c in ?? () #3 0x003e788c in ?? () #4 0x00387ece in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) ====== log end ====== I suspect rebuilding other dependencies manually will fix the problem for me, but I have no enough time to do that. The same application builds fine with Fedora's cross-compile environment, so I've end up with quiet an awkward solution - just copied the binaries from my Fedora setup into Cygwin environemnt and did full rebuild. That worked fine for me. Sorry if I am raising known issue, I know your time is limited. Just wanted to be sure you aware about the issue. Best regards, Konstantin ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ Cygwin-ports-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cygwin-ports-general
