instrumentation

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

Hi, I also have a question regarding the custom post processor.

In the example https://github.com/AFLplusplus/AFLplusplus/blob/stable/custom_mutators/examples/post_library_gif.so.c#L48 it is mentioned that if the post process function returns 0 the input is not sent to the target program and fuzzing is continued. When I tried to do that same the fuzzer throws the error: `Custom_post_process fa

There are many instances of INSTR_CREATE macro documentation saying things like this:

* \param dc  The void * dcontext used to allocate memory for the instr_t.

That should have a # to link up the instr_t type.

Hi,

For safety use, it's better to have null check for all variables which are used in this function.

if (!_sessionPriv.$clientAlarmList) {
    return;
}

↓

if (!_sessionPriv.$clientAlarmList
     || !_sessionPriv.$monitoredItemForAlarmList
     || !_sessionPriv.$subscriptionforAlarmList ) {
    return;
}

https://github.com/node-opcua/node-opcua/blob/master/pack