Massive test failures on 64-bit and 32-bit when running in debug.

On a new (G)linux system

cat /proc/version Linux version 4.19.37-5rodete1-amd64 (glinux-team@google.com) (gcc version 8.0.1 20180414 (experimental) [trunk revision 259383] (Debian 8-20180414-1)) #1 (closed) SMP Debian 4.19.37-5rodete1 (2019-06-20 > 2018)

I am now getting a whole barrage of test failures, in particular when running debug:

The following tests FAILED:
         67 - code_api|linux.syscall_pwait (Failed)
         80 - code_api|linux.sigsuspend (Failed)
         81 - code_api|linux.signest (Failed)
        119 - code_api|client.modules (Failed)
        130 - code_api|client.annotation-concurrency (Failed)
        131 - code_api|client.annotation-concurrency.full-decode (Failed)
        132 - code_api|client.annotation-concurrency.full-decode.tiny-bb (Failed)
        133 - code_api|client.annotation-concurrency.bb-truncate-1 (Failed)
        134 - code_api|client.annotation-concurrency.bb-truncate-2 (Failed)
        135 - code_api|client.annotation-concurrency.prof-pcs (Failed)
        136 - code_api|client.annotation-concurrency-opt (Failed)
        137 - code_api|client.annotation-concurrency-opt.full-decode (Failed)
        138 - code_api|client.annotation-detection (Failed)
        139 - code_api|client.annotation-detection.full-decode (Failed)
        140 - code_api|client.annotation-detection.full-decode.tiny-bb (Failed)
        141 - code_api|client.annotation-detection.bb-truncate-1 (Failed)
        142 - code_api|client.annotation-detection.bb-truncate-2 (Failed)
        143 - code_api|client.annotation-detection-opt (Failed)
        157 - code_api|client.events (Failed)
        158 - code_api|client.events_cpp (Failed)
        175 - code_api|client.null_instrument (Failed)
        181 - code_api|client.drmgr-test (Failed)
        188 - code_api|client.drwrap-test (Failed)
        189 - code_api|client.drwrap-test-callconv (Failed)
        190 - code_api|client.drsyms-test (Failed)
        198 - code_api|client.destructor (Failed)
        231 - code_api|tool.drcov.fib (Failed)
        244 - code_api|tool.drcachesim.threads (Failed)
        245 - code_api|tool.drcachesim.threads-with-config-file (Failed)
        246 - code_api|tool.drcachesim.TLB-threads (Failed)
        248 - code_api|tool.drcachesim.miss_analyzer (Failed)
        308 - code_api|api.static_sideline_FLAKY (Failed)
        311 - code_api|api.static_maps_mixup_novars_FLAKY (Failed)
        314 - code_api,opt_memory|client.events (Failed)
        315 - code_api,opt_speed|client.events (Failed)
        316 - code_api,thread_private|client.events (Failed)
        317 - code_api,disable_traces|client.events (Failed)
        318 - code_api,thread_private,disable_traces|client.events (Failed)
        319 - code_api,no_early_inject|client.events (Failed)
Errors while running CTest

As a side note, the number of release test failures also has increased:

The following tests FAILED: 179 - code_api|client.drmgr-test (Failed) 229 - code_api|tool.drcov.fib (Failed) 303 - code_api|api.static_signal (Failed) 305 - code_api|api.static_sideline_FLAKY (Failed) 308 - code_api|api.static_maps_mixup_novars_FLAKY (Failed) Errors while running CTest

The change appears to be something about the system, not DynamoRIO itself. Rolling back to known better states leads to the same results.