diff options
| author | Treehugger Robot <treehugger-gerrit@google.com> | 2018-01-20 04:48:24 +0000 |
|---|---|---|
| committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | 2018-01-20 04:48:24 +0000 |
| commit | fb96db14d11fa75a5a44162188d6bc441f9491e0 (patch) | |
| tree | 81c34bb8d4d1f0cdbd0dc4dc798ccdc4355d9f7e | |
| parent | 2b66844a0beffff0d2fcf20938e64cdd387131ac (diff) | |
| parent | e61e0cda99503f267b0427ecdd94f4352e963a76 (diff) | |
| download | bionic-fb96db14d11fa75a5a44162188d6bc441f9491e0.tar.gz | |
Merge "Document that dlclose with thread_local is fixed in P."
| -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 | |