[Bug c++/20976] when terminate is called, stack is not unwinded

[jason at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20976

Jason Merrill  changed:

   What|Removed |Added

   Target Milestone|--- |4.6.0
 CC||jason at gcc dot gnu.org
  Known to work||4.6.0
 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from Jason Merrill  ---
The documentation of this implementation-defined behavior was added in 4.6
(r159682).

https://gcc.gnu.org/onlinedocs/gcc/Exception-handling.html

[Bug c++/20976] when terminate is called, stack is not unwinded

[pinskia at gcc dot gnu dot org]

--- Comment #5 from pinskia at gcc dot gnu dot org  2009-05-08 16:21 ---
*** Bug 40066 has been marked as a duplicate of this bug. ***


-- 

pinskia at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||kian dot karas dot dev at
   ||gmail dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20976

[Bug c++/20976] when terminate is called, stack is not unwinded

[pinskia at gcc dot gnu dot org]

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-04-12 
19:23 ---
Ok, this is just implemenation defined behavior.
see 15.3 P 9:
If no matching handler is found in a program, the function terminate() is 
called; whether or not the 
stack is unwound before this call to terminate() is implemenation-defined 
(15.5.1)

So we define it as not unwinding but we don't document this.

Confirmed for documentation.

-- 
   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed||1
   Keywords||documentation
   Last reconfirmed|-00-00 00:00:00 |2005-04-12 19:23:16
   date||
Summary|when exceptions are not |when terminate is called,
   |caught, destructors of local|stack is not unwinded
   |vars are not executed   |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20976