[PATCH] D18167: [ELF/Driver] Avoid a reference to the ELFOptTable after it has gone out of scope

[Rafael Espíndola via llvm-commits]

On 16 March 2016 at 15:28, Kostya Serebryany <kcc at google.com> wrote:
> Interesting.
> Looking at
> https://llvm.org/svn/llvm-project/zorg/trunk/zorg/buildbot/builders/sanitizers/buildbot_functions.sh
> I see export
> ASAN_OPTIONS="check_initialization_order=true:detect_stack_use_after_return=1:detect_leaks=1"
> So, it's already enabled on the bots.
> But, I also see this:
>
>   if [ "$CHECK_LLD" != "0" ]; then
>     echo @@@BUILD_STEP check-lld ${sanitizer_name}@@@
>     # TODO(smatveev): change this to STEP_FAILURE once green
>     (cd ${build_dir} && ninja check-lld) || echo @@@STEP_WARNINGS@@@
>   fi
>
>
> So, check-lld is being run, but errors are not e-mailed to anyone.
> Today there are errors from lsan, msan, and ubsan
> http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fast/builds/11154
>
> Once you (or someone) cleans up these errors we may enable check-lld to
> actually produce errors on buildbot.


Looks like it just went green:

http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fast/builds/11187/steps/check-lld%20msan/logs/stdio

Cheers,
Rafael