diff options
| author | Carlos O'Donell <carlos@redhat.com> | 2016-06-06 14:20:58 -0400 |
|---|---|---|
| committer | Carlos O'Donell <carlos@redhat.com> | 2016-06-06 21:40:25 -0400 |
| commit | 47dd3543d36465496970406da03db5aecdc377ee (patch) | |
| tree | 2288d28761125dcb0b27e150f76314d064decc43 /sysdeps/arm | |
| parent | 3f61232ab337b8162ed1a37558b30ce714dba894 (diff) | |
| download | glibc-47dd3543d36465496970406da03db5aecdc377ee.tar.gz glibc-47dd3543d36465496970406da03db5aecdc377ee.tar.xz glibc-47dd3543d36465496970406da03db5aecdc377ee.zip | |
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.
Diffstat (limited to 'sysdeps/arm')
| -rw-r--r-- | sysdeps/arm/nacl/libc.abilist | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/sysdeps/arm/nacl/libc.abilist b/sysdeps/arm/nacl/libc.abilist index 05605109c8..2f7751d167 100644 --- a/sysdeps/arm/nacl/libc.abilist +++ b/sysdeps/arm/nacl/libc.abilist @@ -1840,3 +1840,4 @@ GLIBC_2.23 fts64_close F GLIBC_2.23 fts64_open F GLIBC_2.23 fts64_read F GLIBC_2.23 fts64_set F +GLIBC_2.24 quick_exit F |