| commit | ff3259b440b3fa55a48cfb6233341c9ff664894a | |
| author | Pete Batard <pete@akeo.ie> | |
| Thu, 7 Jun 2012 10:55:30 +0000 (7 11:55 +0100) | ||
| committer | Pete Batard <pete@akeo.ie> | |
| Thu, 7 Jun 2012 10:55:30 +0000 (7 11:55 +0100) | ||
| tree | 30ad665f9f572d9c4c847d05b47d706191969df6 | treesnapshot (tar.gz zip) |
| parent | 9497ad5711501b6281cc58c1637576be7ceffccd | commitdiff |
Windows: Fix possible crash when using longjmp and gcc 4.6
* With gcc-4.6 the option -fomit-frame-pointer is turned on per default
even for the win32 target. This results in segfaults for any application
using setjmp/longjmp and MSVCRT.dll on WinXP.
See http://gcc.gnu.org/ml/gcc/2011-10/msg00351.html
* Issue reported by Lars Kanis
* With gcc-4.6 the option -fomit-frame-pointer is turned on per default
even for the win32 target. This results in segfaults for any application
using setjmp/longjmp and MSVCRT.dll on WinXP.
See http://gcc.gnu.org/ml/gcc/2011-10/msg00351.html
* Issue reported by Lars Kanis
| configure.ac | diffblobblamehistory | |
| libusb/version_nano.h | diffblobblamehistory |