the Chromium logo

The Chromium Projects

Instrumented libraries for dynamic tools

Instrumented libraries are a part of Chromium's development infrastructure. They are intended to complement sanitizer tools (AddressSanitizer, MemorySanitizer, ThreadSanitizer).

Only Ubuntu Trusty x86_64 is supported at this time.


Sanitizer tools rely on compile-time instrumentation. However, Chromium code may call into system-installed third-party shared libraries, which were not built with the appropriate instrumentation. This is a problem:

To avoid this issue, we've made it possible to make Chromium use sanitizer-instrumented versions of third-party DSOs. By setting a GYP flag, you can either have them built from source during Chromium build, or download pre-built binaries from Google Storage. The list contains ~50 third-party packages, which should cover most of the DSO dependencies of Chrome and tests (enough at least to run MSan without bogus reports).

Using pre-built binaries

Follow the MemorySanitizer instructions.

Note that we don't provide pre-built binaries for every configuration. At this point in time only MSan is supported, with msan_track_origins either 0 or 2.

Building from source

First you need to install build dependencies:

sudo third_party/instrumented_libraries/scripts/

Additionally, if you have gccgo installed, you probably want to remove it with:

sudo apt-get remove --purge gccgo-4.9

With this package installed, running clang++ gives the error cannot find -lstdc++.

To build instrumented libraries from source, add use_locally_built_instrumented_libraries=true to This will add ~50 extra steps to the build. Each step runs a script which does the following:

GOMA is supported (just add use_goma=1).

Adding new packages

You'll need to ping earthdok@ or glider@ to do this. The information below is for reference.

To add a new package, you need to do the following:

Usually you want to use the same configure flags that debian/rules uses.

To rebuild the binaries, run:

third_party/instrumented_libraries/scripts/ all

The entire process will take several hours. For that reason, it is recommended to use --parallel to build all configs concurrently, and -j96 (or whatever value you prefer) to build multiple packages concurrently.

It's a good idea to not do this on Goobuntu. We have a couple GCE instances configured for this. You can also build in an Ubuntu VM.

After uploading the archives to GCS as the script instructs, you'll get several .sha1 files. You should commit those under third_party/instrumented_libraries/binaries/.