instrumentation

When the computer is suspended during a fuzzing session, the time spent in suspended state is counted as a "run time" on a statistics screen. In case fuzzing was running for several hours and then the computer was suspended for several more hours, on one hand I would prefer not restarting the session, on the other hand, now it may be harder to tell how well a harness performs (corpus count vs. run

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

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