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

NDK app crash with -fexceptions, -Os and -fsanitize=address #615

Closed
dxin2015 opened this issue Jan 10, 2018 · 1 comment
Closed

NDK app crash with -fexceptions, -Os and -fsanitize=address #615

dxin2015 opened this issue Jan 10, 2018 · 1 comment
Assignees

Comments

@dxin2015
Copy link

dxin2015 commented Jan 10, 2018

Similar to
#573
and
#360
but this happens without -Oz and does not do dlclose, either.

Removing -fsanitize=address would pass the test

This is a further investigation of
#613
with isolated code and minimal example.

Demo code:

https://github.com/dxin2015/Asan_test_exception
Output:

ASAN:DEADLYSIGNAL

==11865==ERROR: AddressSanitizer: SEGV on unknown address 0x0000000c (pc 0xaefad620 bp >0xbebdbfd8 sp 0xbebdbec8 T0)
==11865==The signal is caused by a READ memory access.
==11865==Hint: address points to the zero page.
ASAN:DEADLYSIGNAL
AddressSanitizer: nested bug in the same thread, aborting.

NDK Version: 16.1.4479499
Build sytem: cmake triggered by gradle, gradle=4.1, gradle plugin=3.0.0, cmake=3.6.4111459
Host OS: Ubuntu 16.04
Compiler: clang++
ABI: armeabi-v7a
STL: libc++_shared
NDK API level: 26
Device API level: 25

@rprichard rprichard self-assigned this Feb 15, 2018
@rprichard
Copy link
Collaborator

Further reduction: https://github.com/rprichard/Asan_test_exception

I think I'll close this issue in favor of the earlier issue #613.

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

2 participants