Integrate libvex into rr
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
For #609. We'll want a libvex preferably
- split out of the valgrind repo. (Not a hard requirement.)
- in a git repo that we can optionally submodule into rr
- scripted to be easily update-able from main V, and able to run V unit tests specific to libvex (if there are any). Bonus points for mirroring entire commit history, in case we have to push any patches relevant to rr, or need to bisect history.
I know an attempt was made to write python bindings for VEX, but I don't know if any other project has already done the work described here.
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 reviewing issue #609 and the existing libvex and Valgrind repository context; the issue mentions a prior attempt at Python bindings but names no rr files or tests. Done means defining a separable libvex git repository or submodule, an update script, and a way to run any libvex-specific VEX unit tests, with commit-history mirroring considered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100