This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/12298] Stack unwind destroys not-yet-constructed object
- From: "raoulgough at yahoo dot co dot uk" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 Sep 2003 11:14:52 -0000
- Subject: [Bug c++/12298] Stack unwind destroys not-yet-constructed object
- References: <20030916120451.12298.raoulgough@yahoo.co.uk>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12298
------- Additional Comments From raoulgough at yahoo dot co dot uk 2003-09-26 11:14 -------
Maybe this a generic sjlj exception handling problem? I'm not too clear on
which compiler releases have used this mechanism, but the mingw compiler I have
certainly does (note the --enable-sjlj-exceptions configure option below).
Maybe the Linux versions mentioned by Wolfgang Bangerth used different EH
mechanism between 3.2 and 3.3/mainline?
$ f:/mingw/bin/gcc -v
Reading specs from f:/mingw/bin/../lib/gcc-lib/mingw32/3.3.1/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=c,c++,f77,objc,ada,java --disable-win32-registry --disable-
shared --enable-sjlj-exceptions --enable-libgcj --disable-java-awt --without-x -
-enable-java-gc=boehm --disable-libgcj-debug --enable-interpreter --enable-hash-
synchronization
Thread model: win32
gcc version 3.3.1 (mingw special 20030804-1)