aboutcode-org / aboutcode-org/tracecode-toolkit-strace
suggestions for improving strace command
Open
enhancement
- Dominant language
- Python
- Stars
- 25
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
For our paper we used the following strace options:
strace -e trace=file,process,dup,dup2,close,pipe,pipe2,fcntl -q -f -s 512
The -e option might be useful to reduce the amount of data that is stored. We actually stored quite a bit of data (512 bytes) per trace call. I don't clearly remember if that was too much or not, but since the paths in the Nix store can be quite long I think that's why ;-)
Contributor guide
Assessment
This issue has not been assessed yet.