From: Alberto L. <al...@na...> - 2002-09-28 13:07:02
|
I didn't get any error message when I click in "No". The program only exists. The same with "Yes". My specs: E:\>g++ -v Reading specs from E:/C/DEV-C/BIN/../lib/gcc-lib/mingw32/3.2/specs Configured with: ../gcc/configure --with-gcc --with-gnu-ld --with-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls --enable-languages=f77,c++,objc,ada --disable-win32-registry --disable-shared Thread model: win32 gcc version 3.2 (mingw special 20020817-1) At 14:01 28/09/02 +0200, you wrote: > >Hi. > >I've discovered that programs built with MinGW's g++ 3.2 dies with >'abnormal program termination' when a Windows callback throws an >exception. > >The trivial Windows GUI program attached below works fine with MinGW >gcc 2.95.3-6, FSF gcc 3.1 configured with --enable-sjlj-exceptions, >Borland 5.5.1 and MSVC++ 6 sp4 > >Build, execute, click on the 'close window' box, say 'no'. > >Of course, I've discovered the problem while working on a "real world" >application <g>. This is a serious drawback. > >The question: is dwarf exception handling supposed to work across >Windows callbacks? > >If the answer to the above is 'No', IMHO MinGW should go back to sjlj >exceptions. > >-- >Oscar |