rust-lang / rust-lang/rust-analyzer
Can not start debug unit test -- undefined symbol: ge�uid, version GLIBC_2.2.5
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
rust-analyzer version: (eg. output of "Rust Analyzer: Show RA Version" command)
rust-analyzer version: 9700addc8 2022-01-17 stable
rustc version: (eg. output of rustc -V)
rustc 1.57.0 (f1edd0429 2021-11-29)
cargo 1.57.0 (b2e52d7ca 2021-10-21)
Failed to start debug session when I click the debug button on my unit test function, the terminal says:
/home/user/temp/hellowrust/target/debug/deps/hellowrust-6b1a6746e6f46ae4: symbol lookup error: /home/user/temp/hellowrust/target/debug/deps/hellowrust-6b1a6746e6f46ae4: undefined symbol: ge�uid, version GLIBC_2.2.5
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
Reproduce the failure by using the debug button on a Rust unit test, starting from the rust-analyzer debug-session entry point and the terminal's undefined-symbol error. Compare the reported rust-analyzer, rustc, and cargo versions while tracing why the session does not start; done means the unit-test debug session launches without this symbol lookup error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100