On 02/07/2016 05:29, Jeffrey Walton wrote:
On Sun, Jun 26, 2016 at 10:33 PM, Jeffrey Walton noloader@gmail.com wrote:
Hi Everyone,
I have a test script from help that repeatedly builds and runs a library under different configurations. The script includes multiple Asan tests.
The Asan tests are producing some findings under ARM32 as shown below. Other platforms do not include Asan findings. In addition, Valgrind does nt produce any findings.
The test program is always built with at least -g2, and sometimes built with -g3. However, I am not seeing the symbolication. According to the GCC folks, asan_symbolize is not required for GCC because it uses libbacktrace. Also see http://bugzilla.redhat.com/show_bug.cgi?id=1250844.
Why am I lacking symbolization, and how do I achieve it?
Mystery solved... GCC 4.8 does not provide a symbolizer.
From a new comment on the GCC bug report (https://bugzilla.redhat.com/show_bug.cgi?id=1250844#c6):
Even with symbolizer you may face some issue with ASAN on ARM. Check this llvm bug report [1].
[1] https://llvm.org/bugs/show_bug.cgi?id=22741
I don't know what is different about things on my CubieTruck5 (Linaro, GCC 4.8.2), but I had to use asan_symbolize provided by Clang/Asan to get symbols for a GCC/Asan finding.
Everything is different in this regard between 4.8.x and 4.9.x. Only the latter has libbacktrace symbolization built in, the former doesn't have any symbolization.
linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain