>> 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]
On 02/07/2016 05:29, Jeffrey Walton wrote:
> On Sun, Jun 26, 2016 at 10:33 PM, Jeffrey Walton 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.
On Sun, Jun 26, 2016 at 10:33 PM, Jeffrey Walton 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
>> 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.
Hi,
2016-06-27 5:33 GMT+03:00 Jeffrey Walton :
> 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
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,