search

ramosian-glider / address-sanitizer

Automatically exported from code.google.com/p/address-sanitizer
0 stars 0 forks source link

Support Android in asan_symbolize #396

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. run asan_symbolize on ASan output from adb logcat

What is the expected output? What do you see instead?
I expect symbolized output but I get raw addresses instead.

Original issue reported on code.google.com by tetra20...@gmail.com on 26 Jun 2015 at 5:45

GoogleCodeExporter commented 9 years ago 
Proposed change to process_line_posix:
-        '^( *#([0-9]+) *)(0x[0-9a-f]+) *\((.*)\+(0x[0-9a-f]+)\)')
+        '^(?:[A-Z]\/[a-z ]*\([0-9 ]+\):)?( *#([0-9]+) *)(0x[0-9a-f]+) 
*\((.*)\+(0x[0-9a-f]+)\)')

How do you guys want me to test this before submit to llvm-commits?

Original comment by tetra20...@gmail.com on 26 Jun 2015 at 5:46

GoogleCodeExporter commented 9 years ago 
I believe the only testing (and only use) we have for asan_symbolize.py is in 
ASan lit tests. Just run those to check you are not breaking other platforms.

For Android, we just push llvm-symbolizer to the device. You can not test adb 
logcat output because we run multiple tests in parallel. Perhaps a test on a 
pre-recorded snippet of adb logcat?

Original comment by euge...@google.com on 26 Jun 2015 at 6:56

GoogleCodeExporter commented 9 years ago 
Adding Project:AddressSanitizer as part of GitHub migration.

Original comment by ramosian.glider@gmail.com on 30 Jul 2015 at 9:06