rust-lang / rust-lang/rust

Debuginfo tests don't control for ambient tools

Open
#126,092 17 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

A-compiletest A-debuginfo A-testsuite C-bug E-hard T-bootstrap WG-debugging
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

The debuginfo tests should probably use a specific debugger, like maybe an lldb we build with the compiler, so that they work consistently. In practice, they have been effectively broken on user's machines by just trying to use whatever is installed.

In other words: just because I use Linux doesn't mean I have gdb installed.

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 locating the debuginfo tests and checking how they choose a debugger on a Linux machine. Compare that behavior with the issue's proposed approach of using a specific debugger, such as an LLDB built with the compiler. Done means the tests no longer depend on whatever debugger happens to be installed on the user's machine and run consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
43/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.