Re: Asan output not symbolized

2016-07-04 Thread Adhemerval Zanella
On 04/07/2016 15:56, Jeffrey Walton wrote: >>> 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

Re: Asan output not symbolized

2016-07-04 Thread Jeffrey Walton
>> 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/

Re: Asan output not symbolized

2016-07-04 Thread Adhemerval Zanella
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. >> >> The Asan tests

Re: Asan output not symbolized

2016-07-02 Thread Jeffrey Walton
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 ARM32 as shown below

Re: Asan output not symbolized

2016-07-02 Thread Jeffrey Walton
Hi Maxim, > Are these full backtraces you got from ASan? If so, do you use stripped > libraries on your system (on Ubuntu, I guess, you do). Could this issue > (https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00132.html) be related to to > your problem? Maybe part of the intermediate solution is to

Re: Asan output not symbolized

2016-07-01 Thread Jeffrey Walton
>> >> AddressSanitizer: stack-buffer-overflow on address 0xbec57b18 at pc >> 0x38c651 bp 0xbec579e0 sp 0xbec579e4 >> >> AddressSanitizer: stack-buffer-overflow on address 0xbedbae9c at pc >> 0x6553f bp 0xbedbae68 sp 0xbedbae6c >> >> AddressSanitizer: stack-buffer-overflow on address 0xbea67b18 at p

Re: Asan output not symbolized

2016-07-01 Thread Jeffrey Walton
>> 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.

Re: Asan output not symbolized

2016-06-27 Thread Maxim Ostapenko
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 as shown below. > Othe