lib/glibc
1
0
Fork 0
mirror of https://sourceware.org/git/glibc.git synced 2025-07-29 11:41:21 +03:00
Code Activity

Bug 20198: quick_exit should not call destructors.

Browse Source 
In C++11 18.5.12 says "Objects shall not be destroyed as a
result of calling quick_exit." In C11 quick_exit is silent
about thread object destruction. Therefore to make glibc
C++ compliant we do not call any thread local destructors.
A new regression test verifies the fix.

I will note that C++11 18.5.3 makes it clear that C++
defines additional requirements for _Exit() to prevent it
from executing destructors.

Given that the point of _Exit() is to terminate the process
immediately it makes sense the C and C++ should line up
and avoid calling destructors.

No failures. New regtest passes.
This commit is contained in:
Carlos O'Donell
2016-06-06 14:20:58 -04:00
parent 3f61232ab3
commit 47dd3543d3
37 changed files with 216 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
sysdeps/unix/sysv/linux/sparc/sparc32/libc.abilist
View File

@ -1963,6 +1963,7 @@ GLIBC_2.23 fts64_open F
GLIBC_2.23 fts64_read F
GLIBC_2.23 fts64_set F
GLIBC_2.24 GLIBC_2.24 A
GLIBC_2.24 quick_exit F
GLIBC_2.24 recvmsg F
GLIBC_2.24 sendmsg F
GLIBC_2.3 GLIBC_2.3 A

1
sysdeps/unix/sysv/linux/sparc/sparc64/libc.abilist
View File

@ -1901,6 +1901,7 @@ GLIBC_2.23 fts64_open F
GLIBC_2.23 fts64_read F
GLIBC_2.23 fts64_set F
GLIBC_2.24 GLIBC_2.24 A
GLIBC_2.24 quick_exit F
GLIBC_2.24 recvmmsg F
GLIBC_2.24 recvmsg F
GLIBC_2.24 sendmmsg F