use_lld broken with msan |
||||
Issue descriptionWhen Chromecast internal builders pulled in the change to use_lld with msan, msan tests started failing with: libosmesa.so: undefined symbol: __msan_maybe_store_origin_8 lib/libsqlite3.so: undefined symbol: __msan_maybe_warning_1 and stack traces weren't getting symbolized. Our GN args: cast_is_debug = true chromecast_branding = "internal" dcheck_always_on = true is_chromecast = true is_component_build = false is_debug = false is_msan = true optimize_for_size = false target_cpu = "x64" use_prebuilt_instrumented_libraries = true
,
Oct 24 2017
Does it help if you roll past https://chromium-review.googlesource.com/730566 ? We needed to disable lld with msan for other reasons.
,
Oct 24 2017
Let me report back; we should pick that up in our roll today and we'll get more results hopefully by EOD
,
Oct 31 2017
,
Feb 22 2018
mbjorge: "EOD" :)
,
Feb 22 2018
/shamecube A classic off-by-121 error Looking at our latest MSAN results, we are no longer seeing the undefined symbol error, so I think this issue is resolved
,
Feb 22 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by mbjorge@google.com
, Oct 24 2017