New issue
Advanced search Search tips

Issue 773437 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 773430



Sign in to add a comment

Package chromeos-config ASAN failure

Project Member Reported by afakhry@chromium.org, Oct 10 2017

Issue description

The amd64-generic-tot-asan-informational [1] builder is currently failing because of the the chromeos-config package. Reason is odr-violation. Here's the output:



chromeos-config-tools-0.0.1-r633:  * ASAN error detected:
chromeos-config-tools-0.0.1-r633:  * =================================================================
chromeos-config-tools-0.0.1-r633:  * ==17==ERROR: AddressSanitizer: odr-violation (0x7f8a5ca84820):
chromeos-config-tools-0.0.1-r633:  *   [1] size=56 'vtable for brillo::FakeCrosConfig' ../../../../../../../../../mnt/host/source/src/platform2/chromeos-config/libcros_config/fake_cros_config.cc
chromeos-config-tools-0.0.1-r633:  *   [2] size=56 'vtable for brillo::FakeCrosConfig' ../../../../../../../../../mnt/host/source/src/platform2/chromeos-config/libcros_config/fake_cros_config.cc
chromeos-config-tools-0.0.1-r633:  * These globals were registered at these points:
chromeos-config-tools-0.0.1-r633:  *   [1]:
chromeos-config-tools-0.0.1-r633:  *     #0 0x7f8a5c97611e  (/var/cache/portage/chromeos-base/chromeos-config-tools/out/Default/cros_config_unittest+0x3e11e)
chromeos-config-tools-0.0.1-r633:  *     #1 0x7f8a5ca3ebab  (/var/cache/portage/chromeos-base/chromeos-config-tools/out/Default/cros_config_unittest+0x106bab)
chromeos-config-tools-0.0.1-r633:  *     #2 0x7f8a5b7446c4  (/lib64/libc.so.6+0x206c4)
chromeos-config-tools-0.0.1-r633:  *     #3 0x7f8a5c9648f8  (/var/cache/portage/chromeos-base/chromeos-config-tools/out/Default/cros_config_unittest+0x2c8f8)
chromeos-config-tools-0.0.1-r633:  * 
chromeos-config-tools-0.0.1-r633:  *   [2]:
chromeos-config-tools-0.0.1-r633:  *     #0 0x7f8a5c97611e  (/var/cache/portage/chromeos-base/chromeos-config-tools/out/Default/cros_config_unittest+0x3e11e)
chromeos-config-tools-0.0.1-r633:  *     #1 0x7f8a5c91f32b  (/var/cache/portage/chromeos-base/chromeos-config-tools/out/Default/lib/libcros_config.so+0x1532b)
chromeos-config-tools-0.0.1-r633:  *     #2 0x7f8a5c720c0b  (/lib64/ld-linux-x86-64.so.2+0xfc0b)
chromeos-config-tools-0.0.1-r633:  *     #3 0x7f8a5c711d79  (/lib64/ld-linux-x86-64.so.2+0xd79)
chromeos-config-tools-0.0.1-r633:  * 
chromeos-config-tools-0.0.1-r633:  * ==17==HINT: if you don't care about these errors you may set ASAN_OPTIONS=detect_odr_violation=0
chromeos-config-tools-0.0.1-r633:  * SUMMARY: AddressSanitizer: odr-violation: global 'vtable for brillo::FakeCrosConfig' at ../../../../../../../../../mnt/host/source/src/platform2/chromeos-config/libcros_config/fake_cros_config.cc
chromeos-config-tools-0.0.1-r633:  * ==17==ABORTING




[1]: https://build.chromium.org/p/chromiumos.chromium/builders/amd64-generic-tot-asan-informational?numbuilds=200
 

Comment 1 by sjg@chromium.org, Oct 10 2017

Can you please explain what this means? How come it is now caught by tests?

Comment 2 by derat@chromium.org, Oct 10 2017

https://github.com/google/sanitizers/wiki/AddressSanitizerOneDefinitionRuleViolation

It's been failing since at least Oct 3 (I didn't look back further); Ahmed is just being awesome and letting you know about it. :-)

Comment 3 by sjg@chromium.org, Oct 10 2017

OK thanks

Comment 4 by vapier@chromium.org, Oct 10 2017

most bots don't run with ASAN and so don't catch as many memory errors

Comment 6 by sjg@chromium.org, Nov 4 2017

Labels: Unibuild

Comment 7 by sjg@chromium.org, Nov 20 2017

Owner: la...@chromium.org
Lann did you already fix this one?

Comment 8 by lannm@google.com, Nov 20 2017

I don't think so, but I can take a look.

Comment 9 by lannm@google.com, Nov 20 2017

Status: WontFix (was: Assigned)
Can't repro, and the test appears green now.
Labels: -Restrict-View-Google

Sign in to add a comment