Skip to content
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

how to solve the problem of Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly. ABORTING #690

Closed
daliands opened this issue Jun 16, 2016 · 4 comments

Comments

@daliands
Copy link

I built addresssanitizer in aosp/5.1.1/external/compiler-rt/lib/asan,,then I found asanwrapper in /system/bin and libclang_rt.asan_arm_android.so in /system/lib.then i push libclang_rt.asan-arm-android.so in system/lib and push app_process in /system/bin/asan。Then I run my asan test apk,it has a shadow memory problem,Sorry for the bad English.

@chefmax
Copy link

chefmax commented Jun 16, 2016

Please check: https://github.com/google/sanitizers/wiki/AddressSanitizer#faq

Q: I'm using dynamic ASan runtime and my program crashes at start with "Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly.".

A1: If you are using shared ASan DSO, try LD_PRELOAD'ing Asan runtime into your program.
A2: Otherwise you are probably hitting a known limitation of dynamic runtime. Libasan is initialized at the end of program startup so if some preceeding library initializer did lots of memory allocations memory region required for ASan shadow memory could be occupied by unrelated mappings.

@yugr
Copy link

yugr commented Jun 16, 2016

@daliands
Copy link
Author

Thank you, @chefmax I have tested LD_PRELOAD at first. but the rom can not start .i will check it later. @yugr I build the rom with make USE_CLANG_PLATFORM_BUILD:=true SANITIZE_TARGET=address -j42,but it does not change anything .

@morehouse
Copy link
Contributor

2 years old, no reproducer. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants