Christian Franke wrote:
Kai Tietz wrote:
Hello,
2013/3/23 Corinna Vinschen schrieb:
Thanks for the testcase. I'm not a gcc expert, so I defer to Kai.
Kai, can you have a look what happens here?
Thanks,
Corinna
yes, this is a gcc bug. it isn't sepcial to cygwin64. It happens
also for x64
Kai Tietz wrote:
Hello,
2013/3/23 Corinna Vinschen schrieb:
Thanks for the testcase. I'm not a gcc expert, so I defer to Kai.
Kai, can you have a look what happens here?
Thanks,
Corinna
yes, this is a gcc bug. it isn't sepcial to cygwin64. It happens
also for x64 mingw, so please file a
Hello,
2013/3/23 Corinna Vinschen corinna-cyg...@cygwin.com:
Thanks for the testcase. I'm not a gcc expert, so I defer to Kai.
Kai, can you have a look what happens here?
Thanks,
Corinna
yes, this is a gcc bug. it isn't sepcial to cygwin64. It happens
also for x64 mingw, so please file
Hello,
2013/3/23 Corinna Vinschen schrieb:
Thanks for the testcase. I'm not a gcc expert, so I defer to Kai.
Kai, can you have a look what happens here?
Thanks,
Corinna
yes, this is a gcc bug. it isn't sepcial to cygwin64. It happens
also for x64 mingw, so please file a regression-bug
On Mar 22 23:08, Christian Franke wrote:
Thanks for providing 64-bit Cygwin.
A 64bit test build of smartmontools 6.1 segfaults after throw (It
uses throw frequently because I replaced 'exit(status)' with 'throw
(int)(status)' during C - C++ migration). Changing the optimization
level from
Thanks for providing 64-bit Cygwin.
A 64bit test build of smartmontools 6.1 segfaults after throw (It uses
throw frequently because I replaced 'exit(status)' with 'throw
(int)(status)' during C - C++ migration). Changing the optimization
level from -O2 to -O1 or -Os fixes the segfault.
I
