diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-10-01 18:42:34 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-10-01 18:42:34 +0200 |
| commit | e40e50ed49a1f7e8d30e3d9b5449425528906c94 (patch) | |
| tree | 2bcbeecb8ca57344242005522b1c979b7ee2cc5a /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | 15b7792a65a5f50d22f77c02cff75f8015c48bc8 (diff) | |
| parent | 1f8bef51e30a087a8b8843c19762952a50087a71 (diff) | |
| download | rust-e40e50ed49a1f7e8d30e3d9b5449425528906c94.tar.gz rust-e40e50ed49a1f7e8d30e3d9b5449425528906c94.zip | |
Rollup merge of #147177 - Walnut356:tuples, r=Mark-Simulacrum
[DebugInfo] Fix MSVC tuple child creation This is a fix for the debugger visualizer scripts For whatever reason, using `CreateChildAtOffset` on the child element sometimes caused issues with pointers (and maybe some other types). The resulting child's memory would be a block 4 bytes too far forward. Creating the child off of the parent `valobj` and using the type definition to get the correct offset seems to fix that. Before: <img width="489" height="136" alt="image" src="https://github.com/user-attachments/assets/fb4cb95c-f199-49a6-8eba-6d3ff486b69a" /> After: <img width="518" height="145" alt="image" src="https://github.com/user-attachments/assets/3f50dbc3-19ca-4fd8-87c5-b4be295f6e7c" /> This shouldn't affect any tests as we don't run debuginfo tests for MSVC afaik
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions