Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Rev b7fd7c95c571 allows a developer to debug a failure in hashmap_test 1. Once
the test fails, rerunning that test will replay the same failure to try to
permit debugging it. But that behavior is extremely undesirable under
TeamCity! In a TeamCity run, don't even check for saved data file.
|
|
|
|
removed some potential data races
got memory stats recording in trace system
|
|
|
|
|
|
|
|
|
|
|
|
|
|
created memory tracking trace type
instrumented a few classes with memory tracking
|
|
|
|
|
|
Debug and RelWithDebInfo builds. Also, reworked the rest of the methods to only apply in cases where the class instance has been initialized.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This is the real viewer-side work that was the motivation for MAINT-2123.
Reviewed with Bao.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|