Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bcc-tools: trace.py syscall trace not working for proccess in container(lxc) #4946

Open
rhjdvsgsgks opened this issue Mar 23, 2024 · 1 comment

Comments

@rhjdvsgsgks
Copy link

rhjdvsgsgks commented Mar 23, 2024

im trying to debug a init proccess in a lxc container. for better reproduce, im using mknod tool instead bellow

with trace 'c:mknodat "%s", arg2' i can see the call to mknodat while im running mknod test c 1 11 out of container.

but if i run the same thing in container. trace.py didnt show me anything. by using strace, i confirmed the mknodat syscall has been send out without any issue.

is this a expected behavior?

im using trace 'filename_create(int dfd, struct filename *name, struct path *path, unsigned int lookup_flags) "%s", name->name' -UK (and find through stack manually) as a alternative now. because do_mknodat not exported and optimized by compiler, which changed signature

version: 5f21a72
kernel version: 6.8.1

@rhjdvsgsgks
Copy link
Author

maybe related to #4854

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant