rr-debugger / rr-debugger/rr

is_rr_supported test binary?

Open
#3,337 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
10.7k
Forks
662
Avg merge
2d 3h
Merged PRs (30d)
2

Description

During my battle yesterday trying to compile rr for cuttlefish arm64, I realized that a simple test binary that just tests for needed perf counters and CPU architecture might save a lot of time before investing effort into getting a full rr build working. We could compile this as a statically-linked PIE with musl, so the same binary could run on almost anything as long as the architecture matches (e.g. Android).

https://git.zv.io/toolchains/musl-cross-make

Thoughts? A "better" solution would be to get rr compiled properly for more target platforms, but that is often more work (which may or may not be useful in the end if it's unsupported).

Contributor guide

Open the contributing guide

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.

Research direction

Start by reviewing the proposed test binary scope and the linked musl-cross-make project. Determine which perf counters and CPU architectures must be checked and whether a statically linked PIE can run on the stated targets. Done means the project has an agreed implementation and validation plan for this preflight binary.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
devtools, operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.