libcompiler-builtins contains DWARF5 debuginfo in 1.62.0

[glandium]

Building Firefox with rustc 1.62.0 on Linux and running it under valgrind makes valgrind emit the following error:

==31382== Valgrind: debuginfo reader: ensure_valid failed:
==31382== Valgrind:   during call to ML_(img_get)
==31382== Valgrind:   request for range [3275670898, +4) exceeds
==31382== Valgrind:   valid image size of 1880027600 for image:
==31382== Valgrind:   "/builds/worker/workspace/obj-build/toolkit/library/build/libxul.so"
==31382==
==31382== Valgrind: debuginfo reader: Possibly corrupted debuginfo file.
==31382== Valgrind: I can't recover.  Giving up.  Sorry.

As of filing, I don't have more information to share yet, but I thought I'd already file it before starting to investigate it next week.

[choccydev]

I am unfamiliar with Valgrind, but i updated a couple hours ago and i can't get LLDB to display local variables while debugging. Maybe related? It worked perfectly fine before the updated and i didn't change anything else.

Tried common fixes, resetting, etc.

[glandium]

This seems to have started somewhere between nightly-2022-04-28 and nightly-2022-04-29... and there's an LLVM update in the range. I'm going to bisect further with the bors builds.

[glandium]

Yep, started on 1388b38.

[glandium]

So... if I build 1388b38 locally, it doesn't reproduce...

[glandium]

The CI change in 278fdf6 had the unintended side effect of shipping libcompiler-builtins with DWARF5 debuginfo, which is not well supported.

[glandium]

For the record, libprofiler_builtins, and librustc-stable_rt.*san.a also have DWARF5 debuginfo.

[glandium]

For the record (bis), my local builds of 1.62 were unaffected despite being compiled with clang 14 because they don't contain debuginfo in those libs at all.