edb icon indicating copy to clipboard operation
edb copied to clipboard

An eBPF program debugger

Results 21 edb issues
Sort by recently updated
recently updated
newest added

Hi, after I enter the command ` edb graph dist/tracee.bpf.core.o tracepoint__raw_syscalls__sys_enter -f dot -o res.dot`. I got the following error: ``` Error: load collection: file dist/tracee.bpf.core.o: section "kprobe/security_file_open": string is...

In the course of developing EDB so far I have encounters a number of bugs, these are often only reproducible after following a very specific set of steps and a...

enhancement

Currently, `list` shows us the source code at the current location. This issues proposes to extend its functionality by adding some optional parameters. It would, for example be handy to...

enhancement

Since #13 and [484f163](https://github.com/dylandreimerink/edb/commit/484f1632fa7526e098f7f0e16378d8ea11ecb866) we have the tools to determine in which function/scope we are and where we came from. The `locals` command uses the current scope to look for...

enhancement

The `step` command we currently have always steps into functions, this is fine if we want to follow execution in detail, but it is very frustrating at times to have...

enhancement

This issue proposes to add commands with which the contents of registers and memory can be updated. The purpose of this feature is to explore conditions which normally don't occur...

enhancement

This issue proposes to add log points, which are a type of "breakpoint" that, instead of actually breaking the program will log a message and/or expression to some log buffer...

enhancement

This issue proposes to add conditional breakpoints, which would allow a user to specify a expression(#16) to a breakpoint. Only when this expression evaluates to `true` would the breakpoint be...

enhancement

A common feature is to be able to perform some basic evaluations on the current program state. This issue proposes to add a `eval`/`exec`/`call` command to the debugger which then...

enhancement

Currently, the only way to know where breakpoints are placed is to look at `breakpoint list` and match the entries there to the code / instructions. It would be nice...

enhancement
good first issue