llvm dev - Apr 2014 - [LLVMdev] Need help reproducing a sanitizer buildbot failure

You need llvm-symbolizer in PATH.
On Apr 11, 2014 3:16 AM, "Diego Novillo" <dnovillo at
google.com> wrote:
> OK, so now I've gotten a build but the output from asan is less than
> helpful:
>
> $ llvm/x/llvm_build_asan/./bin/opt
llvm/x/llvm/test/Other/optimization-remarks-inline.ll
> -inline -pass-remarks=inline -S
> ================================================================>
==6791==ERROR: AddressSanitizer: heap-use-after-free on address
> 0x6040000016a8 at pc 0x1e70553 bp 0x7fff29de4fb0 sp 0x7fff29de4fa8
> READ of size 13 at 0x6040000016a8 thread T0
>     #0 0x1e70552 (/ssd/dnovillo/llvm/x/llvm_build_asan/bin/opt+0x1e70552)
>     #1 0x1e6f3d3 (/ssd/dnovillo/llvm/x/llvm_build_asan/bin/opt+0x1e6f3d3)
>     #2 0x7ab722 (/ssd/dnovillo/llvm/x/llvm_build_asan/bin/opt+0x7ab722)
>     #3 0x19eacc5 (/ssd/dnovillo/llvm/x/llvm_build_asan/bin/opt+0x19eacc5)
>     #4 0x1892f92 (/ssd/dnovillo/llvm/x/llvm_build_asan/bin/opt+0x1892f92)
> [ ... ]
>
> Is there an option for asan to show me source file locations?  Or at least
> function names.  I'm not sure what to do with this.
>
>
> Thanks.  Diego.
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20140411/4849cc87/attachment.html>

Ah, I see.
The bot actually symbolizes the asan's output just fine:
http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap/builds/2959/steps/annotate/logs/stdio

 #1 0x2888c1d in llvm::raw_ostream::write(char const*, unsigned long)
/home/dtoolsbot/build/sanitizer-x86_64-linux-bootstrap/build/llvm/lib/Support/raw_ostream.cpp:332

But since this is a lit test, we don't see the whole output and so this
requires a local rebuild and rerun
(and then you need llvm-symbolizer in PATH).

I wonder if we can configure the lit test runner to print the (tail of)
test output on failure.

--kcc



On Fri, Apr 11, 2014 at 9:59 AM, Evgeniy Stepanov <eugenis at
google.com>wrote:
> You need llvm-symbolizer in PATH.
> On Apr 11, 2014 3:16 AM, "Diego Novillo" <dnovillo at
google.com> wrote:
>
>> OK, so now I've gotten a build but the output from asan is less
than
>> helpful:
>>
>> $ llvm/x/llvm_build_asan/./bin/opt
llvm/x/llvm/test/Other/optimization-remarks-inline.ll
>> -inline -pass-remarks=inline -S
>>
================================================================>>
==6791==ERROR: AddressSanitizer: heap-use-after-free on address
>> 0x6040000016a8 at pc 0x1e70553 bp 0x7fff29de4fb0 sp 0x7fff29de4fa8
>> READ of size 13 at 0x6040000016a8 thread T0
>>     #0 0x1e70552
(/ssd/dnovillo/llvm/x/llvm_build_asan/bin/opt+0x1e70552)
>>     #1 0x1e6f3d3
(/ssd/dnovillo/llvm/x/llvm_build_asan/bin/opt+0x1e6f3d3)
>>     #2 0x7ab722 (/ssd/dnovillo/llvm/x/llvm_build_asan/bin/opt+0x7ab722)
>>     #3 0x19eacc5
(/ssd/dnovillo/llvm/x/llvm_build_asan/bin/opt+0x19eacc5)
>>     #4 0x1892f92
(/ssd/dnovillo/llvm/x/llvm_build_asan/bin/opt+0x1892f92)
>> [ ... ]
>>
>> Is there an option for asan to show me source file locations?  Or at
>> least function names.  I'm not sure what to do with this.
>>
>>
>> Thanks.  Diego.
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>>
>>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20140411/42d86132/attachment.html>

On Fri, Apr 11, 2014 at 3:35 AM, Kostya Serebryany <kcc at google.com>
wrote:
> Ah, I see.
> The bot actually symbolizes the asan's output just fine:
>
>
http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap/builds/2959/steps/annotate/logs/stdio
>
>  #1 0x2888c1d in llvm::raw_ostream::write(char const*, unsigned long)
/home/dtoolsbot/build/sanitizer-x86_64-linux-bootstrap/build/llvm/lib/Support/raw_ostream.cpp:332
>
> But since this is a lit test, we don't see the whole output and so this
> requires a local rebuild and rerun
> (and then you need llvm-symbolizer in PATH).
>
> I wonder if we can configure the lit test runner to print the (tail of)
> test output on failure.
>
Thanks. I've now found and fixed the bug. Another thing that may help in
the future is to have asan display a warning/note when it can't find
llvm-symbolizer. This would help with figuring out why it's giving an
unreadable trace.


Diego.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20140411/89024e18/attachment.html>

On Fri, Apr 11, 2014 at 12:35 AM, Kostya Serebryany <kcc at google.com>
wrote:
>
> I wonder if we can configure the lit test runner to print the (tail of)
> test output on failure.
>
You'd have to teach FileCheck, actually, since it's the one that
consumes
stderr in this case.  Rather than doing that, why not use
*SAN_OPTIONS=log_file=blah.txt, and teach lit to dump that on failure?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20140411/ca2d16f6/attachment.html>