[roll] Roll fuchsia [debugger] Tolerate non-existent threads in OnThreadExiting

This could be the case when we're keeping track of DebuggedProcess
objects, but are not attached to their debugger exception channel to
receive thread starting events, and then at some later point do decide
to attach, but haven't synchronized the threads yet.

Clients are already equipped to handle receiving the notification in
this case.

Original-Fixed: 463317618
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1431994
Original-Revision: 64a7bd282ee9e1eb01a5615bf4b689bf1d055215
GitOrigin-RevId: 9f9c868213d31fad725441dcd162e2b001568972
Change-Id: I5c27590e34fa26bef3fc64a1ffb1d24ffe09d8fc
1 file changed
tree: 57d8296cd8dd379fa0aa0ac4fb156d85a1aa1743
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
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.