| commit | e3acf0998b80fede0c9425d4b9b12a627742ff41 | [log] [tgz] |
|---|---|---|
| author | David 'Digit' Turner <digit@fuchsia.infra.roller.google.com> | Mon Apr 07 13:08:39 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Apr 07 13:10:23 2025 -0700 |
| tree | 75e07d2ad40679304b877058d573ca19ff74f9f1 | |
| parent | 5c535f06e32fee9bffb0ad58e4944d11e01cd74b [diff] |
[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
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.