rust/tests/debuginfo, branch autohttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=auto2025-10-02T06:55:51+00:00codegen: Generate `dbg_value` for the ref statement2025-10-02T06:55:51+00:00dianqkdianqk@dianqk.net2025-06-18T14:04:48+00:00urn:sha1:1bd89bd42e0bb6f29b8af5d6bdf3f756196bb8eetests: Ignore basic-stepping.rs on riscv642025-08-29T08:11:48+00:00Caiweirancai.weiran.zte.com.cn2025-08-29T08:11:48+00:00urn:sha1:a54567e76ce0b32c6d48d019ab4bd9c8a7070933Rollup merge of #145745 - heiher:ignore-basic-stepping, r=lqd2025-08-23T02:00:58+00:00Jacob Prattjacob@jhpratt.dev2025-08-23T02:00:58+00:00urn:sha1:561656db6789caface445d993b015d709ddbb635
tests: Ignore basic-stepping.rs on LoongArch
Rollup merge of #145218 - nilptr:nilptr/feat/lldb-enum-pretty-printer, r=Mark-Simulacrum2025-08-23T02:00:49+00:00Jacob Prattjacob@jhpratt.dev2025-08-23T02:00:49+00:00urn:sha1:5cfdbd6c08681249cab4794366d2ade92e1f7c03
[Debuginfo] improve enum value formatting in LLDB for better readability
> TL;DR: When debugging with CodeLLDB, I noticed enum values were often hard to read because LLDB lists every possible variant, resulting in a verbose and cluttered view, even though only one variant is actually valid. Interestingly, raw enum types display nicely. After some investigation, I found that `&enum` values get classified as `Other`, so it falls back to `DefaultSyntheticProvider`, which causes this verbose output.
## What does this PR do?
This PR contains 2 commits:
1. change the enum value formatting from showing 2 separate fields (`value` for attached data and `$discr$` for the discriminator) to a concise `<readable variant name>: <attached data>` format
2. dereference pointer types in `classify_rust_type` so that it can return more accurate type for reference type
## Self-test proof
Before:
<img width="1706" height="799" alt="before" src="https://github.com/user-attachments/assets/b66c7e22-990a-4da5-9036-34e3f9f62367" />
After:
<img width="1541" height="678" alt="after" src="https://github.com/user-attachments/assets/36db32e2-f822-4883-8f17-cb8067e509f6" />
tests: Ignore basic-stepping.rs on LoongArch2025-08-22T07:58:52+00:00WANG Ruiwangrui@loongson.cn2025-08-22T07:58:52+00:00urn:sha1:d61353ff43a328c9d5116f6dfb5820e852449d11Rollup merge of #145297 - adwinwhite:recursive-debuginfo, r=wesleywiser2025-08-21T05:12:16+00:00Jacob Prattjacob@jhpratt.dev2025-08-21T05:12:16+00:00urn:sha1:537d5f40a6d45c3531df85555952e277977fbaaf
fix(debuginfo): handle false positives in overflow check
Fixes rust-lang/rust#144636.
Duplicate wrappers and normal recursive types can lead to false positives.
```rust
struct Recursive {
a: Box<Box<Recursive>>,
}
```
The ADT stack can be:
- `Box<Recursive>`
- `Recursive`
- `Box<Box<Recursive>>` (`Box` now detected as expanding)
We can filter them out by tracing the generic arg back through the stack, as true expanding recursive types must have their expanding arg used as generic arg throughout.
r? ````@wesleywiser````
feat(lldb debug info): improve enum value formatting in lldb2025-08-17T13:15:18+00:00nilptrnilptr.js@gmail.com2025-08-10T14:16:17+00:00urn:sha1:12eb1a0bce83b569f0500f0a78972a1102906264fix(debuginfo): handle false positives in overflow check2025-08-12T09:13:13+00:00Adwin Whiteadwinw01@gmail.com2025-08-12T09:13:13+00:00urn:sha1:e13e1e4c0c3253d25e2571ed7e58b3a02e28e922Revert "Embed GDB pretty printers in rlibs and dylibs"2025-08-06T18:00:58+00:00bjorn317426603+bjorn3@users.noreply.github.com2025-08-06T18:00:58+00:00urn:sha1:270c1a4d24ba4b244037c3fa1651d17a5f77eae4
This reverts commit b4d923cea0509933b1fb859930cb20784251f9be.
Embed GDB pretty printers in rlibs and dylibs2025-08-06T11:24:43+00:00Sebastian Poeplaupoeplau@adacore.com2025-08-01T11:22:06+00:00urn:sha1:b4d923cea0509933b1fb859930cb20784251f9be
Instead of collecting pretty printers transitively when building
executables/staticlibs/cdylibs, let the debugger find each crate's
pretty printers via its .debug_gdb_scripts section. This covers the case
where libraries defining custom pretty printers are loaded dynamically.