| commit | 527d44cb86c7f6656f8eeefaf78102e650b3caf1 | [log] [tgz] |
|---|---|---|
| author | Derek Bruening <bruening@google.com> | Wed Jul 28 17:08:39 2021 |
| committer | GitHub <noreply@github.com> | Wed Jul 28 17:08:39 2021 |
| tree | 8cfbaf30d46e720e347394cf91266aa193e67f8f | |
| parent | 4882f3a1bb84091992e39a0cd7b28776ce3e5c52 [diff] |
i#5021: Set frozen timestamp at drmemtrace max size (#5029)
Adds a new drmemtrace mechanism to set a frozen timestamp for all
future entries, to avoid huge time gaps when -max_global_trace_refs is
reached but existing thread buffers and exits are not emitted until
much later when the app exits.
Adding a small regression test seems difficult without flakiness as
this involved real-time gaps. Tested manually:
Pre-fix we see a 2s gap before the thread exit:
$ ninja && ctest -V -R max-global
$ bin64/drrun -t drcachesim -simulator_type view -indir suite/tests/tool.drcacheoff.max-global*.dir 2>&1 | grep timestamp
T3427537 <marker: timestamp 13271354817417504>
T3427537 <marker: timestamp 13271354817418955>
T3427537 <marker: timestamp 13271354817624561>
T3427537 <marker: timestamp 13271354817657186>
T3427537 <marker: timestamp 13271354817659466>
T3427537 <marker: timestamp 13271354817664998>
T3427537 <marker: timestamp 13271354817667972>
T3427537 <marker: timestamp 13271354817701187>
T3427537 <marker: timestamp 13271354819175717>
After adding a frozen timestamp:
$ bin64/drrun -t drcachesim -simulator_type view -indir suite/tests/tool.drcacheoff.max-global*.dir 2>&1 | grep timestamp
T3429223 <marker: timestamp 13271355614195474>
T3429223 <marker: timestamp 13271355614196983>
T3429223 <marker: timestamp 13271355614399149>
T3429223 <marker: timestamp 13271355614432167>
T3429223 <marker: timestamp 13271355614434675>
T3429223 <marker: timestamp 13271355614438892>
T3429223 <marker: timestamp 13271355614441260>
T3429223 <marker: timestamp 13271355614474587>
T3429223 <marker: timestamp 13271355614475843>
Fixes #5021
DynamoRIO is a runtime code manipulation system that supports code transformations on any part of a program, while it executes. DynamoRIO exports an interface for building dynamic tools for a wide variety of uses: program analysis and understanding, profiling, instrumentation, optimization, translation, etc. Unlike many dynamic tool systems, DynamoRIO is not limited to insertion of callouts/trampolines and allows arbitrary modifications to application instructions via a powerful IA-32/AMD64/ARM/AArch64 instruction manipulation library. DynamoRIO provides efficient, transparent, and comprehensive manipulation of unmodified applications running on stock operating systems (Windows, Linux, or Android) and commodity IA-32, AMD64, ARM, and AArch64 hardware. Mac OSX support is in progress.
DynamoRIO is the basis for some well-known external tools:
Tools built on DynamoRIO and available in the release package include:
DynamoRIO‘s powerful API abstracts away the details of the underlying infrastructure and allows the tool builder to concentrate on analyzing or modifying the application’s runtime code stream. API documentation is included in the release package and can also be browsed online. Slides from our past tutorials are also available.
DynamoRIO is available free of charge as a binary package for both Windows and Linux. DynamoRIO's source code is available primarily under a BSD license.
Use the discussion list to ask questions.
To report a bug, use the issue tracker.
See also the DynamoRIO home page: http://dynamorio.org/