[roll] Roll fuchsia [debugger] Capture full stacks on some exceptions This changes exception handling in the backend to have different behavior depending on the type of exception we're handling. General exceptions (e.g. crashes, page faults, etc) now always send full stacks, which helps clients make decisions automatically. Also changed are software breakpoints exceptions that are not associated with any of our breakpoints. These can come from things like the gTest framework's assertion failures when running with --gtest_break_on_failure, for example, in addition to being manually typed by a developer. We want cases like these to already have a complete stack trace, when possible. In cases where unwind tables have been stripped from the debugged binary, we may not be able to make full progress with the synchronous target unwinder, and the client will have to do unwinding with the debug info on the host anyway, so this is best effort. Original-Bug: 444070494 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1421434 Original-Revision: 27b56e72dded5b11266f1b4463f7c490a4876e4c GitOrigin-RevId: 796bfc608a02457db150db2eea194517a847588c Change-Id: I46880fe663e3d7ffdb77c099f0dbcc3a42097ac2
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.