This is an archive of the discontinued LLVM Phabricator instance.

[sanitizer-common] Force pickup of llvm-symbolizer from new binaries.
ClosedPublic

Authored by hctim on Dec 15 2020, 3:28 PM.

Details

Summary

It's possible currently that the sanitizer runtimes when testing grab
the path to the symbolizer through *SAN_SYMBOLIZER_PATH=...

This can be polluted by things like Android's setup script. This patch
forces external_symbolizer_path=$new_build_out_dir/llvm-symbolizer when
%env_tool_options is used.

Diff Detail

Event Timeline

hctim requested review of this revision.Dec 15 2020, 3:28 PM
hctim created this revision.
Herald added a project: Restricted Project. · View Herald TranscriptDec 15 2020, 3:28 PM
Herald added a subscriber: Restricted Project. · View Herald Transcript
vitalybuka accepted this revision.Dec 15 2020, 8:43 PM
This revision is now accepted and ready to land.Dec 15 2020, 8:43 PM
This revision was landed with ongoing or failed builds.Dec 16 2020, 6:43 AM
This revision was automatically updated to reflect the committed changes.
hctim added a comment.Dec 16 2020, 9:27 AM

(looks like a broke a bot - LMTAL for an in-flight fix: http://lab.llvm.org:8011/#/builders/37/builds/1311/steps/33/logs/stdio)

hctim added a comment.Dec 16 2020, 2:42 PM

(buildbreak fixed in 30d292ddbb7e)

Also seems to have broken the Android bot even after your fix:

(there is currently a build issue obscuring the breakage in latest builds)

Function symbolization seems to be broken on Android.

Also seems to have broken the Android bot even after your fix:

(there is currently a build issue obscuring the breakage in latest builds)

Function symbolization seems to be broken on Android.

Thanks for the heads up - yeah, we don't push the symbolizer on device on Android and everything's invoked through a wrapper script. Let me fix it up.