Skip to content

Conversation

@Zalathar
Copy link
Member

@Zalathar Zalathar commented Dec 6, 2025


This code takes the compiletest code for discovering an “ambient” gdb in the user's path, and moves it to bootstrap.

One of the eventual goals is to allow compiletest to assume that if it has been asked to run the debuginfo-gdb suite, then it must have been passed an explicit --gdb, though we aren't quite there yet.

r? jieyouxu

@rustbot
Copy link
Collaborator

rustbot commented Dec 6, 2025

Some changes occurred in src/tools/compiletest

cc @jieyouxu

@rustbot rustbot added A-compiletest Area: The compiletest test runner A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) labels Dec 6, 2025
@Zalathar
Copy link
Member Author

Zalathar commented Dec 6, 2025

@bors try jobs=arm-android,x86_64-mingw-1,test-various

@rust-bors

This comment has been minimized.

rust-bors bot added a commit that referenced this pull request Dec 6, 2025
Move ambient gdb discovery from compiletest to bootstrap

try-job: arm-android
try-job: x86_64-mingw-1
try-job: test-various
@rust-log-analyzer

This comment has been minimized.

@Zalathar
Copy link
Member Author

Zalathar commented Dec 6, 2025

@bors try cancel

@rust-bors
Copy link

rust-bors bot commented Dec 6, 2025

Try build cancelled. Cancelled workflows:

@Zalathar
Copy link
Member Author

Zalathar commented Dec 6, 2025

@bors try jobs=arm-android,x86_64-mingw-1,test-various

@rust-bors

This comment has been minimized.

rust-bors bot added a commit that referenced this pull request Dec 6, 2025
Move ambient gdb discovery from compiletest to bootstrap

try-job: arm-android
try-job: x86_64-mingw-1
try-job: test-various
@rust-bors
Copy link

rust-bors bot commented Dec 6, 2025

💔 Test for 8f3e014 failed: CI. Failed jobs:

@Zalathar
Copy link
Member Author

Zalathar commented Dec 7, 2025

Hmm, I had been operating on the assumption that these Android flags were specific to debuginfo, but I guess that’s not the case.

@rustbot author

@rustbot rustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Dec 7, 2025
@rustbot
Copy link
Collaborator

rustbot commented Dec 7, 2025

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

While some of this information is needed by debugger discovery, it is also
needed by non-debuginfo tests, so the code doesn't belong in the `debuggers`
module.
@Zalathar
Copy link
Member Author

Zalathar commented Dec 7, 2025

@bors try jobs=arm-android,x86_64-mingw-1,test-various

@rust-bors

This comment has been minimized.

rust-bors bot added a commit that referenced this pull request Dec 7, 2025
Move ambient gdb discovery from compiletest to bootstrap

try-job: arm-android
try-job: x86_64-mingw-1
try-job: test-various
@rust-bors
Copy link

rust-bors bot commented Dec 7, 2025

☀️ Try build successful (CI)
Build commit: 4b032b4 (4b032b4478f08e5e0432c515980a127dad60ed98, parent: d427ddfe90367eaa6d2ed7bb8a16559f0230f47a)

@Zalathar
Copy link
Member Author

Zalathar commented Dec 7, 2025

@rustbot ready

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Dec 7, 2025
Copy link
Member

@jieyouxu jieyouxu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment on lines +24 to +25
// Otherwise, fall back to whatever gdb is sitting around in PATH.
// (That's the historical behavior, but maybe we should require opt-in?)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remark: I'm 100% in favor of opt-in, but that's a separate change.

@jieyouxu
Copy link
Member

jieyouxu commented Dec 7, 2025

@bors r+ rollup

@bors
Copy link
Collaborator

bors commented Dec 7, 2025

📌 Commit 8f35bd1 has been approved by jieyouxu

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Dec 7, 2025
Zalathar added a commit to Zalathar/rust that referenced this pull request Dec 8, 2025
Move ambient gdb discovery from compiletest to bootstrap

- Follow-up to rust-lang#148099

---

This code takes the compiletest code for discovering an “ambient” `gdb` in the user's path, and moves it to bootstrap.

One of the eventual goals is to allow compiletest to assume that if it has been asked to run the debuginfo-gdb suite, then it *must* have been passed an explicit `--gdb`, though we aren't quite there yet.

r? jieyouxu
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-compiletest Area: The compiletest test runner A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants