rust/tests/debuginfo/issue-57822.rs, branch masterhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=master2025-08-01T20:04:59+00:00Remove the omit_gdb_pretty_printer_section attribute2025-08-01T20:04:59+00:00bjorn317426603+bjorn3@users.noreply.github.com2025-07-31T14:56:49+00:00urn:sha1:ae2f8d921654f01e008824385fb1e1d7b36ce705
Disabling loading of pretty printers in the debugger itself is more
reliable. Before this commit the .gdb_debug_scripts section couldn't be
included in dylibs or rlibs as otherwise there is no way to disable the
section anymore without recompiling the entire standard library.
Convert lldbg- to lldb-2024-08-18T21:00:33+00:00Ben Kimockkimockb@gmail.com2024-08-18T21:00:33+00:00urn:sha1:22ed23d680fbb50c90992b03e50968e7bce6f373Delete redundant gdb-version requirements and related comments2024-08-18T20:58:25+00:00Ben Kimockkimockb@gmail.com2024-08-17T22:00:49+00:00urn:sha1:156088f8a86679ec5a342d5e7ebf17f468c805c1Implement lldb formattter for "clang encoded" enums (LLDB 18.1+)2024-05-06T00:53:02+00:00Vladimir Makayevvmakaev@fb.com2024-04-23T01:55:29+00:00urn:sha1:fb2d9cdfc54aea306223992e13ce4b2278d9f0c6
Summary:
I landed a fix last year to enable `DW_TAG_variant_part` encoding in LLDBs (https://reviews.llvm.org/D149213). This PR is a corresponding fix in synthetic formatters to decode that information.
This is in no way perfect implementation but at least it improves the status quo. But most types of enums will be visible and debuggable in some way.
I've also updated most of the existing tests that touch enums and re-enabled test cases based on LLDB for enums.
Test Plan:
ran tests `./x test tests/debuginfo/`. Also tested manually in LLDB CLI and LLDB VSCode
Other Thoughs
A better approach would probably be adopting [formatters from codelldb](https://github.com/vadimcn/codelldb/blob/master/formatters/rust.py). There is some neat hack that hooks up summary provider via synthetic provider which can ultimately fix more display issues for Rust types and enums too. But getting it to work well might take more time that I have right now.
Error on using `yield` without also using `#[coroutine]` on the closure2024-04-24T08:05:29+00:00Oli Scherergit-spam-no-reply9815368754983@oli-obk.de2024-04-11T13:15:34+00:00urn:sha1:aef0f4024aec24fd7e53dbc51883457e44fe17ce
And suggest adding the `#[coroutine]` to the closure
Use explicit LLDB commands instead of `print`/`p` aliases.2024-03-15T14:38:03+00:00Markus Reiterme@reitermark.us2024-03-15T14:05:57+00:00urn:sha1:96431e4b822ff82268bf3f2bbbb7aacf2abc5761Remove LLDB persistent results in `compiletest`.2024-03-14T16:34:58+00:00Markus Reiterme@reitermark.us2024-03-10T13:55:58+00:00urn:sha1:75fba9d574dfd85d9046ddda67d2da2da86ce61c[AUTO_GENERATED] Migrate compiletest to use `ui_test`-style `//@` directives2024-02-22T16:04:04+00:00许杰友 Jieyou Xu (Joe)jieyouxu@outlook.com2024-02-22T12:10:29+00:00urn:sha1:6e48b96692d63a79a14563f27fe5185f122434f8s/generator/coroutine/2023-10-20T21:14:01+00:00Oli Scherergit-spam-no-reply9815368754983@oli-obk.de2023-10-19T21:46:28+00:00urn:sha1:e96ce20b34789d29e925425da6cf138927b80a79s/Generator/Coroutine/2023-10-20T21:10:38+00:00Oli Scherergit-spam-no-reply9815368754983@oli-obk.de2023-10-19T16:06:43+00:00urn:sha1:60956837cfbf22bd8edd80f57a856e141f7deb8c