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.

Is your feature request related to a problem? Please describe.

When starting a nodejs process with pm2 using node-opcua on Windows 10 a Windows Prompt windows pops ups each time when "node-opcua-pki" package runs child_process.exec() method. The exec process is calling openssl.
There are two occurances: lib/misc/install_prerequisite.ts:98 and lib/pki/toolbox.js:123

**Describe

Aug	SEP	Oct
	14
2020	2021	2022

instrumentation

Here are 500 public repositories matching this topic...

frida / frida

raphw / byte-buddy

sensepost / objection

google / mtail

jacoco / jacoco

prometheus / client_python

coverlet-coverage / coverlet

google / orbit

openzipkin / brave

AFLplusplus / AFLplusplus

ChromeDevTools / devtools-frontend

AppMetrics / AppMetrics

DynamoRIO / dynamorio

prometheus / client_java

spring-cloud / spring-cloud-sleuth

rabbitstack / fibratus

iddoeldor / frida-snippets

dpnishant / appmon

node-opcua / node-opcua

RRZE-HPC / likwid

QBDI / QBDI

chuan-yun / Molten

beam-telemetry / telemetry

otobus / event_bus

Flank / flank

SimonKagstrom / kcov

inspectIT / inspectIT

openzipkin-contrib / zipkin-go-opentracing

openzipkin / zipkin-go

frida / frida-core

Improve this page

Add this topic to your repo