Derek Bruening
Derek Bruening
We'd like to be able to write out new core-sharded drmemtrace files for the result of software thread interleaving on virtual cores from the trace scheduler. The plan is to...
The 32-bit version failed once: https://ci.appveyor.com/project/DynamoRIO/dynamorio/builds/21162519 ``` [00:09:36] test 213 [00:09:36] Start 213: code_api|tool.reuse_distance [00:09:36] [00:09:36] 213: Test command: C:\projects\dynamorio\build\build_debug-internal-32\bin32\drrun.exe "-s" "90" "-quiet" "-debug" "-use_dll" "C:/projects/dynamorio/build/build_debug-internal-32/lib32/debug/dynamorio.dll" "-exit0" "-stderr_mask" "0xC" "-msgbox_mask"...
On multiple arches, GA CI builds have many warnings like this while building elfutils: ``` : warning: "_FORTIFY_SOURCE" redefined : note: this is the location of the previous definition ```
This is a feature request to run pytype on the handful of python scripts as part of our automated tests. We run it internally, so an upstream check would prevent...
The Linux client.detach_test was just added in PR #6513 and it is failing (non-deterministically) on x86-64. https://github.com/DynamoRIO/dynamorio/actions/runs/7381905578/job/20080993968?pr=6531 ``` Test #185: code_api|client.detach_test ......................................***Failed Required regular expression not found. Regex=[^starting thank you...
A run on GA CI suddently saw 81 failures. The virtualization changed, or something else was updated on the VM's? These all seem to be new flaky failures with maybe...
Recently this warning was popped up on I believe every single suite result: https://github.com/DynamoRIO/dynamorio/actions/runs/7648183861/job/20840516372?pr=6583 ``` WARNING: maximum warning/error limit hit for debug-internal-64! Manually verify whether it succeeded. debug-internal-64: 9 tests...
Quoting from https://github.com/DynamoRIO/dynamorio/pull/6544#issuecomment-1883354811 > All standalone decode/encode functions should be available in libdynamorio. Looking at dr_set_sve_vector_length() and dr_get_sve_vector_length() in encode_api.h: they are missing DR_API specifiers and this is why they...
To attach DR to an existing process with the drmemtrace client, today the drcachesim launcher cannot be used and the client has to be directly referenced. This works ok for...
Some common metrics for workload characterization are based purely on opcodes and would fit in as additions to the existing opcode_mix analyzer: + branch density + memory density: we have...