about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
diff options
context:
space:
mode:
authorGuillaume Gomez <guillaume1.gomez@gmail.com>2024-06-29 14:07:22 +0200
committerGitHub <noreply@github.com>2024-06-29 14:07:22 +0200
commit38983df5c7bab68242b061fbd9eaf071fedfa921 (patch)
treec4ae96f6c79111c281eb0b7f20b34eeba475aa19 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
parent0886faaeeaa836ee3c66310bd3b8edcc52737aa5 (diff)
parenta6ef91e41425ba315cb11ee20a99f3fdc714c6cf (diff)
downloadrust-38983df5c7bab68242b061fbd9eaf071fedfa921.tar.gz
rust-38983df5c7bab68242b061fbd9eaf071fedfa921.zip
Rollup merge of #127112 - ChrisDenton:lldb, r=Kobzol
Bootstrap: Don't get output if `lldb --version` errors

fixes #126892

`Command` can error in two ways: the OS can fail to run the binary at all or else the binary can return an error exit code. Unfortunately the distinction between the two is not clear cut. The OS may succeed in starting the binary but it may still error before `main` (e.g. if a necessary library fails to load) and this will be reported via the exit code.

Fortunately this case is simpler. We can assume that `lldb --version` will only ever error if there's a startup issue of some kind. so both kinds of errors are caused by the OS. Thus it's safe for us to treat them equally for the sake of this specific check.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions