aboutcode-org / aboutcode-org/tracecode-toolkit-strace

suggestions for improving strace command

Open
#2 2 comments 0 reactions 0 assignees View on GitHub
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

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.