-
Notifications
You must be signed in to change notification settings - Fork 992
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Leak sanitizer support for Android on arm64 #379
Comments
Reported by |
Reported by |
Reported by |
Reported by |
Reported by |
Reported by |
Reported by
|
I am currently trying to use described functionality in my android library:
However, the linking stage fails: How can I link from Android.mk to implementation of that function? [edit] In fact, I wonder what is the current status of Leak sanitizer support for Android. There is couple of information scattered thorough the wiki/Internet when regarding debugging applications/so libraries, but no concise description. E.g.:
I managed to compile my library with address sanitizer support on armeabi, armeabi-v7a, arm64-v8a, x86; build for x86_64 failed. [edit2] Upon running my library for arm64-v8a on an emulator it crashes with: |
LSan does not work on Android at the moment. I'm not sure how much work is left, probably a subset of things listed in this comment: Currently LSan is disabled for Android in the upstream (llvm / cmake) build system, and it is not included in the android prebuilt libraries (the ones you find in the NDK) either. Regarding your "dlopen failed" error, for this library to appear on device (or emulator) you'd need to run asan_device_setup as per ASan documentation. And, again, there is no LSan there. |
Thank you for your comment @eugenis. |
Valgrind has some sort of memory profiler (massif). I don't know how well
it works on android.
…On Thu, Mar 30, 2017 at 10:04 PM, Piotr ***@***.***> wrote:
Thank you for your comment @eugenis <https://github.com/eugenis>.
I am currently stuck with a memory-related issue in my NDK component on
Android. I hoped I could resolve that with Leak Sanitizer. Are you aware of
any other tools that might be helpful in this case?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#379 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAZuSh_xO0lMlu_RT1-j4NjS5dNVWhMVks5rrIlvgaJpZM4MudPz>
.
|
Just curious, are there any technical blockers for enabling LSan on Android Aarch64? At a first glance I can see TLS supporting caveats, but for beginning we can just disable thread local caches in LSan runtime and exclude static TLS from root set (I just don't know how Android libc implements it). |
No blockers. It should be quite easy, we just never had time to finish the
job.
TLS implementation is different from glibc, of course, but it is quite
simple. Excluding it from root set would create false positive reports
though.
The fact that android apps never finish normally (they catch SIGKILL
instead) means the will be no automatic leak report, but the tool would
still be usable for standalone executables and
through __lsan_do_leak_check() interface.
…On Fri, Mar 31, 2017 at 3:50 PM, chefmax ***@***.***> wrote:
Just curious, are there any technical blockers for enabling LSan on
Android Aarch64? At a first glance I can see TLS supporting caveats, but
for beginning we can just disable thread local caches in LSan runtime and
exclude static TLS from root set (I just don't know how Android libc
implements it).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#379 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAZuSgzREm-JrFPxGj6zK-MQlhKakmOJks5rrYMogaJpZM4MudPz>
.
|
Ping. Any progress on this since last year? |
Nope. |
LSAN still does not work for aarch64-clang on Android 8.0 |
Any progress on this over the last three years? |
ASAN+LSAN should work for Android 30+ (aarch64 and x86_64)
(no HWASAN+LSAN yet tho)
…On Fri, Aug 27, 2021, 4:40 AM Tianqi Xu ***@***.***> wrote:
Any progress on this over the last three years?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#379 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANONE6NKFML67VR32D46JLT65FOPANCNFSM4DFZ2PZQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
I tried the NDK25C, and the error |
seems not working for me~ |
Originally reported on Google Code with ID 379
Reported by
vairavans
on 2015-03-06 23:47:18The text was updated successfully, but these errors were encountered: