diff options
author | Elliott Hughes <enh@google.com> | 2018-01-19 10:33:41 -0800 |
---|---|---|
committer | Elliott Hughes <enh@google.com> | 2018-01-19 10:33:41 -0800 |
commit | e61e0cda99503f267b0427ecdd94f4352e963a76 (patch) | |
tree | 3d4151231cb1fb25e554a8ec35b3bc5081720af4 /android-changes-for-ndk-developers.md | |
parent | 0d63a3c233040af004cc470d5f76547f3adc0148 (diff) |
Document that dlclose with thread_local is fixed in P.
Bug: https://github.com/android-ndk/ndk/issues/360
Test: N/A
Change-Id: Ib9807045bd3206fa3cd300ab70ebed93c73a58e4
Diffstat (limited to 'android-changes-for-ndk-developers.md')
-rw-r--r-- | android-changes-for-ndk-developers.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/android-changes-for-ndk-developers.md b/android-changes-for-ndk-developers.md index 48800caf1..e4eb48a85 100644 --- a/android-changes-for-ndk-developers.md +++ b/android-changes-for-ndk-developers.md @@ -389,7 +389,7 @@ adb shell setprop debug.ld.all dlerror,dlopen Android allows `dlclose` to unload a library even if there are still thread-local variables with non-trivial destructors. This leads to crashes when a thread exits and attempts to call the destructor, the -code for which has been unloaded (as in [issue 360]). +code for which has been unloaded (as in [issue 360], fixed in P). [issue 360]: https://github.com/android-ndk/ndk/issues/360 @@ -397,8 +397,8 @@ Not calling `dlclose` or ensuring that your library has `RTLD_NODELETE` set (so that calls to `dlclose` don't actually unload the library) are possible workarounds. -| | Pre-M | M+ | -| ----------------- | -------------------------- | ------- | -| No workaround | Works for static STL | Broken | -| `-Wl,-z,nodelete` | Works for static STL | Works | -| No `dlclose` | Works | Works | +| | Pre-M | M+ | P+ | +| ----------------- | -------------------------- | ------- | ----- | +| No workaround | Works for static STL | Broken | Works | +| `-Wl,-z,nodelete` | Works for static STL | Works | Works | +| No `dlclose` | Works | Works | Works | |