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
So it seems like the problem only occurs with rust-lldb.
Probably this is due to the lack of Rust patches in rust-lldb. AFAIU the Rust patches still have not been added to rust-lldb (I remember this related issue rust-lang/lldb#20).
To fix this problem, the following code should be used insted:
However, I believe that rust-lldb should use Rust patches not only to avoid this specific problem but to provide a much better debugging experience, with proper type rendering (e.g. i32 instead of int), some expression evaluation support, and so forth. It is really unfortunate that Rust debugging support is not maintained enough except for some independent forks, for example, https://github.com/vadimcn/llvm-project/commits/rust-lldb and CLion's LLDB.
I may be misunderstanding you, but rust-lldb is just a shell script that runs the system lldb. Building lldb with patches was removed a long time ago (#62592), and I suspect is not coming back in the foreseeable future.
@ehuss Oh, that's even worse since macOS LLDB has very poor Rust support. I believe that debugging support is crucial for any compiled programming language, surely including Rust. So it would be really great to consider shipping rust-enabled LLDB and, more importantly, to maintain and improve Rust support in both GDB and LLDB.
Activity
artemmukhin commentedon Feb 6, 2021
@ehuss I checked the issue with two different LLDB:
rust-lldbshipped with1.51.0-nightlyby adding the following code to the
StdHashMapSyntheticProvider#updatemethod:rust-lldbLLVM upstream with Rust patches
So it seems like the problem only occurs with
rust-lldb.Probably this is due to the lack of Rust patches in
rust-lldb. AFAIU the Rust patches still have not been added torust-lldb(I remember this related issue rust-lang/lldb#20).To fix this problem, the following code should be used insted:
I've opened a PR with these changes: #81834.
However, I believe that
rust-lldbshould use Rust patches not only to avoid this specific problem but to provide a much better debugging experience, with proper type rendering (e.g.i32instead ofint), some expression evaluation support, and so forth. It is really unfortunate that Rust debugging support is not maintained enough except for some independent forks, for example, https://github.com/vadimcn/llvm-project/commits/rust-lldb and CLion's LLDB.ehuss commentedon Feb 6, 2021
I may be misunderstanding you, but
rust-lldbis just a shell script that runs the system lldb. Building lldb with patches was removed a long time ago (#62592), and I suspect is not coming back in the foreseeable future.artemmukhin commentedon Feb 6, 2021
@ehuss Oh, that's even worse since macOS LLDB has very poor Rust support. I believe that debugging support is crucial for any compiled programming language, surely including Rust. So it would be really great to consider shipping rust-enabled LLDB and, more importantly, to maintain and improve Rust support in both GDB and LLDB.
Rollup merge of rust-lang#81834 - ortem:fix-LLDB-hashmap-pretty-print…