search

google / sanitizers

AddressSanitizer, ThreadSanitizer, MemorySanitizer
Other
11.5k stars 1.04k forks source link

ASAN_OPTION=log_path does not function properly on Android #1135

Open tysmith opened 5 years ago

tysmith commented 5 years ago

It appears that setting log_path does not redirect log output to specified path consistently and when it does not include the trackback information.

Here is an example of incomplete output:

1|generic_x86_64:/ $ cat /sdcard/sanitizer_logs/report.log.8064                               
=================================================================
==8064==ERROR: AddressSanitizer: SEGV on unknown address 0x611b6d2ec56c (pc 0x75522ad4e506 bp 0x7fff49619190 sp 0x7fff496190e0 T0)
==8064==The signal is caused by a READ memory access.

We are able to get a fully symbolized ASan log in logcat with out any issue.

eugenis commented 5 years ago

Hi Tyson,

could you provide a reproducer? Does it happen with applications, or native binaries as well? Does it affect regular ASan bug reports (like use-after-free) or SEGV crashes only?

On Tue, Aug 20, 2019 at 2:57 PM Tyson Smith notifications@github.com wrote:

It appears that setting log_path does not redirect log output to specified path consistently and when it does not include the trackback information.

Here is an example of incomplete output:

1|generic_x86_64:/ $ cat /sdcard/sanitizer_logs/report.log.8064

==8064==ERROR: AddressSanitizer: SEGV on unknown address 0x611b6d2ec56c (pc 0x75522ad4e506 bp 0x7fff49619190 sp 0x7fff496190e0 T0) ==8064==The signal is caused by a READ memory access.

We are able to get a fully symbolized ASan log in logcat with out any issue.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.