diff options
| author | ruuda <ruuda@google.com> | 2016-01-11 06:49:06 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2016-01-11 14:50:30 +0000 |
| commit | f57f47aa398e6ccd03b1888a176fe59e8a5cdea2 (patch) | |
| tree | 1eacb1ca39149f9901adc8641359b05c6dcb7d1c /base/trace_event/trace_event_impl.cc | |
| parent | 14ef868b836f7c2121c8976c88964ff27a19cfa7 (diff) | |
| download | chromium_src-f57f47aa398e6ccd03b1888a176fe59e8a5cdea2.zip chromium_src-f57f47aa398e6ccd03b1888a176fe59e8a5cdea2.tar.gz chromium_src-f57f47aa398e6ccd03b1888a176fe59e8a5cdea2.tar.bz2 | |
[Tracing] Add lookup support to AllocationRegister
This adds a |Get| method to |AllocationRegister| which can be used to
change the context and size of an allocation after it has been inserted.
One possible use case of this is to post-annotate allocations with type
information, when this information is not available to the allocator,
but it is later in the program.
Because |AllocationRegister::Allocation| is now exposed mutably, its
|address| member has been made const. The hash of the address has to
match the bucket in which the |Allocation| is stored, so after insertion
the address must not be changed. This is enforced by making the member
const, at the cost of a few const violations in the implementation of
|AllocationRegister|.
BUG=574756
Review URL: https://codereview.chromium.org/1574493002
Cr-Commit-Position: refs/heads/master@{#368583}
Diffstat (limited to 'base/trace_event/trace_event_impl.cc')
0 files changed, 0 insertions, 0 deletions