suggestions for improving strace command

Open
#2 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
linux

Research direction

The issue names a strace invocation but no repository file, test, or entry point. First clarify whether the desired outcome is changing the traced syscall filters or reducing the -s 512 output, then locate the code that assembles or runs this command. Done should be an agreed change with a test or documented measurement showing the intended data reduction.

Written by the indexing model from the issue text.

Description

enhancement

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 ;-)

Dominant language
Python
Stars
25
Forks
8
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/tracecode-toolkit-strace

All issues in aboutcode-org/tracecode-toolkit-strace

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.