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

invalid user access in action #16

Open
reverseXiang opened this issue May 6, 2023 · 0 comments
Open

invalid user access in action #16

reverseXiang opened this issue May 6, 2023 · 0 comments

Comments

@reverseXiang
Copy link

I use dtrace on a mac with M2 chip. When I trace the same application with dtrace, everything works fine when executing simple logic, but when running complex logic, it reports an error "invalid user access in action".

It seems that dtrace can't track complex scenarios, even if it's just a probe function. When the program runs to very complex logic, the dtrace script can only support very simple logic, a little bit more complex will report an error, this drawback seems to be very limiting. Is there a way to make dtrace work in complex scenarios as well, it seems to be too limited now.

I just try to trace syscall::stat64:entry or syscall::sysctl:entry, but they all failed incomplex scenarios, like multiple calls to the api in a short period of time.

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