Closed jianghupt closed 2 days ago
Honestly, you shouldn't.
If you want the kind of debugging your get from a debug build, you need to set
[rust]
optimize = 0
But please read this paragraph: https://github.com/rust-lang/rust/blob/b5723af3457b9cd3795eeb97e9af2d34964854f2/config.example.toml#L460
Honestly, you shouldn't.
If you want the kind of debugging your get from a debug build, you need to set
[rust] optimize = 0
But please read this paragraph:
I tried it, but the variable still cannot be printed. [rust] optimize = false
debug = true isn't really sufficient for an interactive debugging experience. You need debuginfo-level = 2 (the default with debug = true is debuginfo-level = 1) to get variable information.
debug = true isn't really sufficient for an interactive debugging experience. You need debuginfo-level = 2 (the default with debug = true is debuginfo-level = 1) to get variable information.
thank you, you are right
I compiled https://github.com/rust-lang/rust/ ./x.py build --stage2 . And set [rust] debug=true [llvm] assertins=true
Then I debugged it through lldb, and the command :fr v did not display the variables
How should I make lldb display the variables