cmd/cgo/internal/testsanitizers: ASAN symbolization problems for LUCI's older gcc versionswith DWARF 5 #72752
Labels
BugReport
Issues describing a possible bug in the Go implementation.
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
In the LUCI infrastucture used for Golang testing, we use system images that have baked-in versions of GCC. At the moment for linux-amd64 this means version 10 of GCC, including corresponding versions of various runtime libraries needed to support GCC (e.g. libcc.a, libgcc_s.so, and so on).
In the process of migrating the Go compiler+linker to generate DWARF version 5, we discovered that the asan tests in
cmd/cgo/internal/testsanitizers
were failing on linux/amd64 LUCI builders with symbolization problems. Here is an example failure:Asan is correctly reporting a problem, but getting the file/line wrong when DWARF 5 is used (DWARF 4 has no such issue). Later versions of the runtime (e.g. libasan.so.8 as opposed to libasan.so.6) don't seem to have this problem.
Filing this issue to describe the prolem, and to make a note of the fact that it would be nice to get the GCC version baked into our LUCI images updated to something more modern (GCC 10 is a 2020-vintage release that is no longer supported/updated).
The text was updated successfully, but these errors were encountered: