[roll] Roll fuchsia [unwinder][CFI] Prefer using debug_frame over eh_frame

When generated, the debug_frame will contain more detailed unwinding
information than eh_frame will. This is typically attributed to binary
sizes since eh_frame is an allocated segment which will be optimized to
contain the minimum amount of information necessary while debug_frame is
not subject to such optimizations and therefore will usually contain
more information.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1195598
Original-Revision: f7074e68735ff1878242f1c3eca557fdb3e45e10
GitOrigin-RevId: 4507be587c0de7bd1a72b12ab8a16e9eb8fac2f7
Change-Id: Ie8edaae890fba393bb24f4a5265b802c462d2ebc
1 file changed
tree: 23a4ab1cdec4292d5f55f85a9d5f24c0d8d47aab
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

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.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.