[roll] Roll fuchsia [debugger] Support unwinding from the host

This changes the default behavior of zxdb's unwinding strategy to use
the host's access to full debugging information to help the unwinder use
CFI strategies as often as possible.

The main motivation is the desire to strip target binaries of unwind
tables completely, leaving frame pointers and shadow call stack as the
main two methods of unwinding on the target. This is undesirable during
live debugging while we have access to debugging information which may
include unwind tables which typically provide higher quality backtraces
than frame pointer heuristics or SCS which loses almost all register
context.

Some headers must be modified to not include unwinder headers in paths
that end up also including LLVM headers, which will conflict with elf.h
provided by the sysroot.

Original-Fixed: https://fxbug.dev/292107156
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1172993
Original-Revision: 7de1ba83fcd432be4013d79da1c88d76a9082e63
GitOrigin-RevId: de58d1d3c617a351ff0661b665857c995af18027
Change-Id: I13b7d91cac665475ff0c8b1d5477a8e48ec0d907
1 file changed
tree: 545c729d4b3a8be075a9363ae28f0b8054c2e54f
  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.