invalid user access in action #16
Description
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.