We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
在Android上,如果内核未开启DEBUG_FS的时候,没有/sys/kernel/debug目录,如果使用ebpfmanager编写程序,那么将无法运行任何kretprobe/kprobe程序
/sys/kernel/debug
同时内核未开启DEBUG_FS的时候,/sys/kernel/tracing下面也没有名为available_filter_functions的文件
/sys/kernel/tracing
available_filter_functions
可以考虑通过读取/proc/kallsyms来作为fallback方案获取信息?
/proc/kallsyms
The text was updated successfully, but these errors were encountered:
其实是有读取/proc/kallsyms的,但是在没有上面的debug目录的时候,提前返回了
ebpfmanager/probe.go
Line 382 in 801c655
Sorry, something went wrong.
感谢反馈,我近期看下二者之间的差异。
你测试过在未开启DEBUG_FS下,自己改为/proc/kallsyms的效果吗?
DEBUG_FS
我没有做什么修改,仅仅是将上面那一行return err注释调,然后编译使用,没有什么问题。
return err
不过我仍然在使用ebpfmanager v0.3.0,没有在最新版上测试过。
pr里提了,辛苦试试。
Successfully merging a pull request may close this issue.
在Android上,如果内核未开启DEBUG_FS的时候,没有
/sys/kernel/debug
目录,如果使用ebpfmanager编写程序,那么将无法运行任何kretprobe/kprobe程序同时内核未开启DEBUG_FS的时候,
/sys/kernel/tracing
下面也没有名为available_filter_functions
的文件可以考虑通过读取
/proc/kallsyms
来作为fallback方案获取信息?The text was updated successfully, but these errors were encountered: