You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a discussion that notes in VSCode that people are getting an error/warning about debug information formatters with codelldb on Windows.
Developers are steered to CodeLLDB by the vscode Rust ecosystem; the codelldb note that is referred to from that bug says that 'as it is assumed that users will primarily use WinDbg or Microsoft Visual Studio's debugger for this target' - I think that this assumption is wrong.
It would be great to include the rust debug information formatters for codelldb with the msvc toolchain.
The text was updated successfully, but these errors were encountered:
Rust formatters were a part of codelldb until 1.11, at which point they were deliberately replaced with the formatters distributed by rust itself to decrease the maintenance burden on codelldb.
Rust did not include LLDB and GDB formatters with *-msvc distributions for some reason. As of this pr, that is no longer the case. While the formatters will exist in *-msvc distributions, they still don't function very well. That is actively being worked on by myself and a few others. In the meantime, they're just python scripts so they can altered/copied/replaced to improve their functionality locally.
There is a discussion that notes in VSCode that people are getting an error/warning about debug information formatters with codelldb on Windows.
Developers are steered to CodeLLDB by the vscode Rust ecosystem; the codelldb note that is referred to from that bug says that 'as it is assumed that users will primarily use WinDbg or Microsoft Visual Studio's debugger for this target' - I think that this assumption is wrong.
It would be great to include the rust debug information formatters for codelldb with the msvc toolchain.
The text was updated successfully, but these errors were encountered: