commit | 704bc82504e53c450098fdf8b9f2545d086bf5fe | [log] [tgz] |
---|---|---|
author | Ryan <rsavitski@google.com> | Tue Mar 31 02:31:13 2020 +0100 |
committer | Ryan Savitski <rsavitski@google.com> | Tue Mar 31 01:36:33 2020 +0000 |
tree | 6edcfe906f7a962e19363608d98947e24da134a7 | |
parent | de6d9fd4428c078ddbf5526203cf3d00d1d8602c [diff] |
Ban PERFETTO_EINTR(close(...)), which is actively incorrect This is a surprisingly tangled topic, since POSIX left the behaviour on EINTR unspecified, and implementations diverged. See e.g. http://crbug.com/269623 for more background. Fun side question that follows: do we need to bother with complicating base::ScopedFile with EINTR comparisons to avoid the CHECK on close from firing in very unlikely/impossible(?) scenarios? Change-Id: I77633d63e5855ed2c27c5498a79798b3d8cdfc53
Perfetto is an open-source project for performance instrumentation and tracing of Linux/Android/Chrome platforms and user-space apps.
See www.perfetto.dev for docs.
See /docs/contributing.md for instructions.
The source-of-truth repo is Android's Gerrit. The GitHub repo is a read-only mirror.
You can reach us on our Discord channel. If you prefer using IRC we have an experimental Discord <> IRC bridge synced with #perfetto-dev
on Freenode.