forked from chromium/chromium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[tracing] Fix all places passing non-void* pointers to TRACE_EVENT.
Passing pointers to to TRACE_EVENT without being explicitly converted to void* is going to be disallowed. With TracedValue v2 (http://bit.ly/traced-value-v2), if a reference or pointer to an object are passed TRACE_EVENT will call WriteIntoTracedValue method for this object. This patch prepares for that by ensuring no non-void* pointers are passed to TRACE_EVENT to avoid confusion between "write the value of this pointer" and "serialise underlying object" cases. R=eseckler@chromium.org BUG=1137154 Change-Id: Ibf6c03a5311a4a7dd3070983d81fa52fe5407618 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2678146 Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Eric Seckler <eseckler@chromium.org> Commit-Queue: Kentaro Hara <haraken@chromium.org> Commit-Queue: Alexander Timin <altimin@chromium.org> Auto-Submit: Alexander Timin <altimin@chromium.org> Cr-Commit-Position: refs/heads/master@{#851582}
- Loading branch information
Alexander Timin
authored and
Chromium LUCI CQ
committed
Feb 8, 2021
1 parent
d32c53a
commit fb70a2d
Showing
28 changed files
with
200 additions
and
160 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.