云微

Thanks!

The documents have been moved to https://github.com/eunomia-bpf/eunomia.dev/blob/main/docs/bpftime So please update the documents there

Related: #160

Maybe you can first update the documents for bpftimetool? https://github.com/eunomia-bpf/bpftime/tree/master/tools/bpftimetool You can create a new markdown file in the eunomia.dev repo, and updated the https://github.com/eunomia-bpf/eunomia.dev/blob/main/mkdocs.yaml for that. The website will...

You can create a new markdown file like https://github.com/eunomia-bpf/eunomia.dev/blob/main/docs/bpftime/documents/co-re.md in https://github.com/eunomia-bpf/eunomia.dev/blob/main/docs/bpftime/documents/, add details about bpftimetool, and update the https://github.com/eunomia-bpf/eunomia.dev/blob/main/mkdocs.yaml for the new doc.

What about attach_ctx class? Is it possible to implement all uprobe/syscall related code outside of runtime target and runtime dir? If we can do that, is it a better solution?...

So Maybe we can create two targets? - /attach/uprobe - /attach/syscalls The attach is a new dir under the project root. And the user can specify which one to compile...

Shall we come up with some better name for Uprobe attach manager? Maybe attach_ctx back or attach_target, attach_events? Some background: - The eBPF runtime can be embedded in a shared...

Yes, `uprobe_attach_impl` should be split into an individual target. Can you describe the full dependency and classes inheritance of all the modules/cmake targets you think may be correct? I think...

And also, can we add the new attach event at load time? So it's not statically compiled. For example, we have three kinds agent.so: 1. one is compiled with uprobe...