Title
Unclear specification of effects of signal handling
Status
c++11
Section
6.9.1 [intro.execution]
Submitter
GB

Created on 2010-08-06.00:00:00 last changed 96 months ago

Messages

Date: 2010-11-15.00:00:00

[Voted into the WP at the November, 2010 meeting.]

Date: 2010-08-15.00:00:00

Proposed resolution (August, 2010):

Change 6.9.1 [intro.execution] paragraph 6 as follows:

When the processing of the abstract machine is interrupted by receipt of a signal, the values of objects which are neither

  • of type volatile std::sig_atomic_t nor

  • lock-free atomic objects (31.5 [atomics.lockfree])

are unspecified during the execution of the signal handler, and the value of any object not in either of these two categories that is modified by the handler becomes undefined.

Date: 2010-08-06.00:00:00
N3092 comment GB 7

The current wording of 6.9.1 [intro.execution] paragraph 6 could be read as saying that any signal would leave the program in an unspecified state after completing.

History
Date User Action Args
2014-03-03 00:00:00adminsetstatus: fdis -> c++11
2011-04-10 00:00:00adminsetstatus: dr -> fdis
2010-11-29 00:00:00adminsetmessages: + msg3139
2010-11-29 00:00:00adminsetstatus: ready -> dr
2010-08-23 00:00:00adminsetmessages: + msg2750
2010-08-06 00:00:00admincreate