[roll] Roll fuchsia [fdio] Deliberately leak static client connections

The fdio library lazily creates and stores client connections to various
Fuchsia services in order to implement many fdio, POSIX, and libc
interfaces. Some Fuchsia programs call exit() from one thread while
other threads are executing and calling in to these routines. Thus fdio
must not destruct these objects at static destruction time or these
other threads would crash in confusing ways. Instead, we leak these
objects intentionally.

Original-Fixed: 117875
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/779803
Original-Revision: c7a1e593f8666460a728e249f3ca5490c422bd1b
GitOrigin-RevId: 489df8d17b3b7c3e21c35bb7d979725b25e234d0
Change-Id: I492647f92a9b4ac95aff4858ced7f3d7cf2a2c79
1 file changed
tree: 2d9cbea97bbe26d1402416711433898e75174bd6
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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 via the IRC channel #fuchsia on Freenode.

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.