ilmanzo / ilmanzo/binarycoverage_callgrind
let the python script run gdb, without requiring any extra step
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
as we did with `callgrind_annotate` , we can move the gdb function list to the python script, and avoid also having to write a temporary file
Contributor guide
No contributing guide indexed for this repository
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 Python script and the existing callgrind_annotate handling to understand how the function list is currently passed through a temporary file. The work is done when the script can run gdb and supply the function list directly, without requiring an extra temporary-file step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100