-
-
Notifications
You must be signed in to change notification settings - Fork 15k
Bootstrap panics if lldb fails to start #126892
Copy link
Copy link
Closed
Labels
A-contributor-roadblockArea: Makes things more difficult for new or seasoned contributors to RustArea: Makes things more difficult for new or seasoned contributors to RustC-bugCategory: This is a bug.Category: This is a bug.O-windowsOperating system: WindowsOperating system: WindowsT-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Metadata
Metadata
Assignees
Labels
A-contributor-roadblockArea: Makes things more difficult for new or seasoned contributors to RustArea: Makes things more difficult for new or seasoned contributors to RustC-bugCategory: This is a bug.Category: This is a bug.O-windowsOperating system: WindowsOperating system: WindowsT-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Type
Fields
Give feedbackNo fields configured for issues without a type.
Running
./x test tests/ui --stage 1on Windows I get:This seems especially unfortunate because (as far as I know) ui tests don't require lldb. It works fine if there's no lldb in
PATHat least.This is ultimately an LLVM issue caused by not installing/shipping its own dependencies (in this case Python310). However, bootstrap shouldn't crash here. It should be treated similarly to lldb not existing unless it is actually necessary,