It would be helpful if the lcov generated reports could generate relative paths. My use case is that I am generating coverage reports from a docker image and then using VS Code Coverage Gutters which supports relative paths to view the coverage. But it doesn't work because the absolute paths on the docker c

The memtrace* sample clients use drutil_expand_rep_string, but the instrace* ones do not. This can confuse users: https://groups.google.com/g/dynamorio-users/c/HR4pX6lwP_I

As discussed in the discord channel. Having a whitelist/blacklist approach where you can tell to (not)instrument specific libraries in QEMU mode. For example by passing library names in an env variable. Something like INSTRUMENT_QEMU_BLACKLIST="libc.so,another.so".
Could be done by replacing all the checks if (cur_loc < afl_code_start || cur_loc >= afl_code_end) with the traverse of a list (in

Refactor host -> guest context switch assembly codes that have been duplicated when we introduced AVX support.