[roll] Roll fuchsia [build][api] Support files without build-id value or file.
It turns out that we have a few ELF binary artifacts without a
.note.gnu.build-id section, this happens for at least two types
of cases:
- Host go binaries.
- Special binaries that are linked explicitly
with -Wl,--build-id=none (e.g. the dynamic linker, or
several specialized Zircon binaries).
Meanwhile, some targets declare an elf_build_id_file path,
but never write anything there.
This fixes the logic to ignore entries in the debug_symbols.json
file where there is no build_id in the binary (first case), or
when the build_id_file content is empty (second case).
After this, the following should normally list all the debug symbol
files, with their build-id values, corresponding to the last build's
artifacts:
```
fx build
build/api/client print_debug_symbols --last-build-only --resolve-build-ids
```
+ Fix shared libraries wrapper to Use `elf_build_id_file` instead of
`elf_build_id` to point to the file containing the GNU BuildID value.
Original-Bug: 404208759
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1243324
Original-Revision: 48be0d87aabed31154daf2b213f321877b4b1221
GitOrigin-RevId: 7553e0d9bd8a6a5fca4289209bf7f46b86ab5d67
Change-Id: I69396166a11dc9d6e1cb4a881044dc2deb1f9ae5
diff --git a/stem b/stem
index 959d939..1dcbf98 100644
--- a/stem
+++ b/stem
@@ -11,7 +11,7 @@
githooks="integration/git-hooks"
remote="https://fuchsia.googlesource.com/fuchsia"
gerrithost="https://fuchsia-review.googlesource.com"
- revision="6c57fc6855920f91ed14f519f47bc5804daf7b6f"
+ revision="48be0d87aabed31154daf2b213f321877b4b1221"
/>
</projects>
<hooks>
