Reconsider debugger discovery for debuginfo test suite
Open
Nobody has claimed this yet.
A-compiletest
A-debuginfo
A-testsuite
C-bug
T-bootstrap
T-compiler
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
E.g. don't discover some random lldb from PATH when it's not explicitly configured, maybe explicitly asking for which debugger versions the user wants is the way-to-go, even if that requires more initial setup.
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 locating the debuginfo test suite and its current debugger-discovery entry point. Review how an unconfigured lldb is selected from PATH and determine the intended configuration and version-selection behavior. Done means the suite no longer silently uses an unintended debugger and the chosen setup is documented by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100