Using debuginfo for `pid` provider probes
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 189
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
See also https://github.com/oracle/dtrace-utils/issues/84 and https://github.com/oracle/dtrace-utils/issues/96.
With SystemTap, one can attach based on line number and function name if debug info is available, AFAIK (https://blogs.oracle.com/linux/post/getting-started-with-systemtap-on-oracle-linux).
I see two usecases:
- Printing argument or variable contents (not having to lookup which argument
pathis) - Being able to add a probe which I could already do via instruction offsets in a more friendly manner
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the related dtrace-utils issues 84 and 96, the SystemTap reference, and the linked instruction-offset documentation. Determine how debuginfo could support line numbers, function names, and argument or variable contents for pid provider probes; done means the two described use cases work in a documented, testable way.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- observability-sre, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100