From 47dd3543d36465496970406da03db5aecdc377ee Mon Sep 17 00:00:00 2001 From: Carlos O'Donell Date: Mon, 6 Jun 2016 14:20:58 -0400 Subject: Bug 20198: quick_exit should not call destructors. 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. --- stdlib/Versions | 3 +++ 1 file changed, 3 insertions(+) (limited to 'stdlib/Versions') diff --git a/stdlib/Versions b/stdlib/Versions index 60b628d47a..9c06b43986 100644 --- a/stdlib/Versions +++ b/stdlib/Versions @@ -109,6 +109,9 @@ libc { GLIBC_2.18 { __cxa_thread_atexit_impl; } + GLIBC_2.24 { + quick_exit; + } GLIBC_PRIVATE { # functions which have an additional interface since they are # are cancelable. -- cgit 1.4.1