[LLVMdev] Need help reproducing a sanitizer buildbot failure

[Diego Novillo]

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>