This is an unofficial snapshot of the ISO/IEC JTC1 SC22 WG21 Core Issues List revision 110b. See http://www.open-std.org/jtc1/sc22/wg21/ for the official list.
[Voted into WP at March, 2010 meeting.]
14.2 [except.throw] paragraph 4 says,
When the last remaining active handler for the exception exits by any means other than throw; the temporary object is destroyed and the implementation may deallocate the memory for the temporary object...
With std::current_exception() (17.9.7 [propagation] paragraph 7) , it might be possible to refer to the exception object after its last handler exits (if the exception object is not copied). The text needs to be updated to allow for that possibility.
Proposed resolution (September, 2009):
Change 14.2 [except.throw] paragraph 4 as follows:
The memory for the
temporary copy of the exception being thrownis allocated in an unspecified way, except as noted in 22.214.171.124.2 [basic.stc.dynamic.allocation]. The temporary persists as long as there is a handler being executed for that exception. In particular, ifa handler exits by executing a throw; statement, that passes controlto another handler for the same exception , so the temporary remains. Whenthe last remaining active handler for the exception exits by any means other than throw; the temporary object is destroyed and theimplementation may deallocate the memory for the temporaryobject; any such deallocation is done in an unspecified way. The destruction occurs immediately after the destruction of the object declared in the exception-declaration in the handler.