-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
strings in predicates failures #198
Comments
The problem doesn't seem to be restricted to predicates, using |
I'm hitting this as well. Another test case (because more is always better):
|
Super annoying bug, working on this now. |
@danobi, do you still working on this? |
@williangaspar it's still on my todo list. Feel free to take it from me if you want |
Yes, this is super annoying so a fix would be good to see soon. We do need more than this though for pattern matching in a predicate. I often need to do the equivalent of 't:syscall:whatever/comm == "hhvm*" as I am interested in a range of processes whose name begins with "hhvm". In DTrace you could do something like /strstr(execname, "hhvm") != NULL/ if my memory serves me right. |
By the error message, it seems |
@tyroguru this seems like a useful feature. Do you mind opening another issue for it? |
👍 |
There's two invocations here that fail differently, but I think one bug may be responsible.
To start with, this works:
That's the PID of a bash shell. Matching on the process name, and including -v:
Ok, looks like an alignment issue of the "bash" string.
Now changing the action performed:
This time it compiles, but no events fire.
The text was updated successfully, but these errors were encountered: