pa-fazil
/
android_bionic
mirror of https://github.com/fazilsheik96/android_bionic.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Document the dlclose/thread locals with non-trivial destructors problem. 

Bug: https://github.com/android-ndk/ndk/issues/360
Test: N/A
Change-Id: I964a6c9abd1ae65d74c6aee1c842b2f3d24b5556
This commit is contained in:
Elliott Hughes 2017-10-25 15:02:36 -07:00
parent 88c5ddb6d2
commit bcbce9b453
1 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
android-changes-for-ndk-developers.md
View File

@ -376,3 +376,22 @@ adb shell setprop debug.ld.all dlerror,dlopen
```
enables logging of all errors and dlopen calls
## dlclose interacts badly with thread local variables with non-trivial destructors
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]).
[issue 360]: https://github.com/android-ndk/ndk/issues/360
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 |