-
Notifications
You must be signed in to change notification settings - Fork 6
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
README fails to mention what strace-analyzer
's output looks like.
#34
Comments
Yes, you're right. I will address address this. |
I've updated the README, feel free to take a peek at it in the wip/next branch. I'm going to cut a new release soon anyway, that's why I'm still keeping it in that branch. |
Now it is more clear - it aggregates reads and writes by filepaths. Should it be made more clear that mmap-based file access would not be counted? I think at least it should mark files ever mmapped with some asterisk.
Are there plans to implement more things? For example, networking sockets conversations may be aggregated in a similar way (including counters for usage of advanced features like AF_UNIX's SCM_RIGHTS). |
|
I myself don't intend to implement anything else at the moment. Feel free to contribute, though! |
Closing since the README is updated with the latest release. |
It shows how to call strace-analyzer, but does not show or explain what do I get from it.
By the way, does it work well for non-file things, like NETLINK sockets or tricky ioctls? README should also clarify what the tool can and what cannot do.
The text was updated successfully, but these errors were encountered: