rustup update did not update certain components properly

[HeWhoHeWho]

Verification

• I searched for recent similar issues at https://github.com/rust-lang/rustup/issues?q=is%3Aissue and found no duplicates.
• I am on the latest version of Rustup according to https://github.com/rust-lang/rustup/tags and am still able to reproduce my issue.

Problem

rustup update updated cargo, cargo-clippy, cargo-fmt, rustc, rustdoc & rustfmt, but did not update/install: rust-analyzer, rust-gbd, rust-gbdgui, rust-lldb properly.

Note: I had to install rust-analyzer manually via rustup component add rust-analyzer (Notice the date modified difference in the screenshot below)

Steps

1. Perform rustup update to update Rust from previous version (0.19.0 in my case) to 0.191.

Possible Solution(s)

No response

Notes

Using latest Visual Studio C++ Build tools

Rustup version

1.91.0

Installed toolchains

stable-x86_64-pc-windows-msvc

OS version

Windows 11 Pro 26100.6899

[rami3l]

@HeWhoHeWho Hello, and thanks for the report!

IIRC rustup can detect which components don't need update and as a result it won't update those. This is particularly true for rust-gdb and rust-lldb since they are just direct wrappers over gdb and lldb and hardly need changes.

If you are talking about the fact that they are not shown as executables, maybe there is a problem in the distribution format rather than rustup itself (cc @ChrisDenton for further confirmation regarding the Windows platform; probably related to existing issue: #2838).

As for rust-analyzer I am not quite sure what is happening, but it is true that the default profile doesn't include this component.

[ChrisDenton]

It does seem odd to me that rustc is distributing bash shell scripts for the msvc target. Maybe I'm forgetting a reason for doing that but I think it's not going to work in any case because I'm pretty sure it doesn't ship the actual lldb with rustc (which is what the script calls by default).

[ChrisDenton]

Ok, it would work if: using a msys2/cygwin shell and you've installed lldb or gdb separately. So yeah, that part is #2838. We'd either need to make rust-gdb (in .cargo/bin) a shell script or try to invoke msys2 manually via rustup. Either option would require some design work. But that's probably better discussed on #2838.