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

7
stdlib/exit.c
View File

@ -31,13 +31,14 @@ DEFINE_HOOK (__libc_atexit, (void))
void
attribute_hidden
__run_exit_handlers (int status, struct exit_function_list **listp,
bool run_list_atexit)
bool run_list_atexit, bool run_dtors)
{
/* First, call the TLS destructors. */
#ifndef SHARED
if (&__call_tls_dtors != NULL)
#endif
__call_tls_dtors ();
if (run_dtors)
__call_tls_dtors ();
/* We do it this way to handle recursive calls to exit () made by
the functions registered with `atexit' and `on_exit'. We call
@ -101,6 +102,6 @@ __run_exit_handlers (int status, struct exit_function_list **listp,
void
exit (int status)
{
__run_exit_handlers (status, &__exit_funcs, true);
__run_exit_handlers (status, &__exit_funcs, true, true);
}
libc_hidden_def (exit)