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

Hi,

I'd like to check if a session is active for a subscription.
If I got it right, hasSession() is prepared for this purpose.
But it can't be accessed because it doesn't exist in [interface](https://github.com/node-opcua/node-opcua/blob/master/packages/node-o

Just lost my status screens with few billions of execs :(
So, my ideas:

1. Can we store all the fuzzer stats as shown in status screen, and then restore it when resuming (with both AFL_AUTORESUME and '-i' option) ? If it somehow affects or depends on inner state of AFL++ instance, can we restore this inner state too?
2. Can we prevent random Ctrl+C presses for example, by asking to confirm? You

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