Yichun Zhang

Results 34 issues of Yichun Zhang

Sorry if it is something obvious, but is it possible to detach the "rr record" process from the target process? So that the target process can continue running (like a...

Currently, when I hit Ctrl-C to quit `bpftime load`, it only destructs the global shm without cleaning up the target process's injected code and data: ``` ^C14:59:56 pid=622114 malloc calls:...

bug
enhancement
help wanted

Consider a bpf userland program traces itself like this: ```C ... #include #include int main(int argc, char *argv[]) { ... obj = bpf_object__open_file("hello.bpf", NULL); ... prog = bpf_object__find_program_by_name(obj, "hello"); ......

bug

When running the unit test suite of bpftime on Fedora Linux x86_64, I'm seeing 2 test cases failing consistently: ``` =============================================================================== test cases: 16 | 14 passed | 2 failed...

bug
help wanted

I've noted that I cannot see any log messages from SPDLOG in the target process's agent code. For example, I have to patch the `ringbuf::reserve` function like below actually to...

bug
documentation

Currently, the bpftime build always includes libbpf and Linux kernel interoperability, which we don't need in our use cases. It would be nice to have a build option to exclude...

enhancement
good first issue
help wanted

I've noticed that right after I run the `bpftime attach PID` command, the target process's output stream will immediately have the extra output lines like these: ``` [2024-01-27 14:54:25.459] [info]...

bug
good first issue
help wanted

I'm getting the following error with uprobe + llvm jit: ``` [2024-01-28 01:12:03][info][707874] Created uprobe/uretprobe perf event handler, module name /500g-a/git/ebpf-plus/libbpf/uprobes/a.out, offset 1126 [2024-01-28 01:12:03.112] [info] [agent.cpp:66] Entering bpftime agent...

bug
good first issue
help wanted

The global shm is leaking because there is no way to release a particular eBPF program individually. We can only free up everything like this: ``` $ bpftimetool remove [2024-01-26...

enhancement

I tried to use the system environment variable to control the log level of bpftime but it won't work, at least for the `bpftime attach` command: ``` $ SPDLOG_LEVEL=Error bpftime...

bug