--- Comment #5 from pinskia at gcc dot gnu dot org 2006-04-10 16:28 ---
*** This bug has been marked as a duplicate of 11813 ***
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #1 from mlazar at kma dot zcu dot cz 2006-04-10 03:37 ---
Created an attachment (id=11232)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11232action=view)
c++ part of bug-demonstration program
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27098
--- Comment #2 from mlazar at kma dot zcu dot cz 2006-04-10 03:38 ---
Created an attachment (id=11233)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11233action=view)
c part of bug-demonstration program
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27098
--- Comment #3 from mlazar at kma dot zcu dot cz 2006-04-10 03:41 ---
Created an attachment (id=11234)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11234action=view)
Compiler versions and configurations
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27098
--- Comment #4 from mlazar at kma dot zcu dot cz 2006-04-10 04:15 ---
I observed that if the c source is compiled with -foptimize-sibling-calls -O
options (on i686 in gcc 4.0.3), the exception is catched.
So in this case, the terminate() function call:
gcc -c helper.c
g++ helper.o
