[roll] Roll fuchsia [bt][snoop] Collect and report controller core dumps Monitor incoming HCI traffic for vendor-specific crash diagnostic events and automatically trigger the collection of core dumps. When a crash event is detected, bt-snoop creates a VMO and captures subsequent HCI traffic into a PCAP-formatted core dump. The collection window is debounced to avoid spamming reports. After the window closes, the collected dump is submitted as an attachment to the fuchsia.feedback.CrashReporter service. Additionally, restructure state management using a CrashState struct to track concurrent dump collections across devices, and adopt fuchsia_async timing primitives to ensure reliable unit test behavior. Original-Bug: 488367063 Multiply: bt-snoop-unittests Test: 1) fx test bt-snoop-unittests 2) fx shell bt-fct-hci raw 1c fd 01 f5 3) verify crash report at go/crash/79d398af0543da41 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1529980 Original-Revision: acc1183aff3ece8c56f01d6b4c648b207bc10117 GitOrigin-RevId: 8c67000059a2bd417b26c1e6336abe91a9c0d9b4 Change-Id: Ic0c264388700899548ad8aa48730c34da8236b2e
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.