Skip to content

Conversation

Walnut356
Copy link
Contributor

@Walnut356 Walnut356 commented Sep 30, 2025

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:

image

After:

image

This shouldn't affect any tests as we don't run debuginfo tests for MSVC afaik

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Sep 30, 2025
@rustbot
Copy link
Collaborator

rustbot commented Sep 30, 2025

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@Mark-Simulacrum
Copy link
Member

@bors r+

@bors
Copy link
Collaborator

bors commented Oct 1, 2025

📌 Commit 1f8bef5 has been approved by Mark-Simulacrum

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Oct 1, 2025
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Oct 1, 2025
[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
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Oct 1, 2025
[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
bors added a commit that referenced this pull request Oct 1, 2025
Rollup of 8 pull requests

Successful merges:

 - #146593 (Allow specifying multiple bounds for same associated item, except in trait objects)
 - #147177 ([DebugInfo] Fix MSVC tuple child creation)
 - #147195 (iter repeat: add tests for new count and last behavior)
 - #147202 (Swap order of `resolve_coroutine_interiors` and `handle_opaque_type_uses`)
 - #147204 (Refactor ArrayWindows to use a slice)
 - #147219 (Add proper error handling for closure in impl)
 - #147226 (include `outer_inclusive_binder` of pattern types)
 - #147230 (Fix typo in 'unfulfilled_lint_expectation' to plural)

r? `@ghost`
`@rustbot` modify labels: rollup
@bors bors merged commit e40e50e into rust-lang:master Oct 1, 2025
10 checks passed
@rustbot rustbot added this to the 1.92.0 milestone Oct 1, 2025
rust-timer added a commit that referenced this pull request Oct 1, 2025
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
github-actions bot pushed a commit to model-checking/verify-rust-std that referenced this pull request Oct 9, 2025
…iaskrgr

Rollup of 8 pull requests

Successful merges:

 - rust-lang#146593 (Allow specifying multiple bounds for same associated item, except in trait objects)
 - rust-lang#147177 ([DebugInfo] Fix MSVC tuple child creation)
 - rust-lang#147195 (iter repeat: add tests for new count and last behavior)
 - rust-lang#147202 (Swap order of `resolve_coroutine_interiors` and `handle_opaque_type_uses`)
 - rust-lang#147204 (Refactor ArrayWindows to use a slice)
 - rust-lang#147219 (Add proper error handling for closure in impl)
 - rust-lang#147226 (include `outer_inclusive_binder` of pattern types)
 - rust-lang#147230 (Fix typo in 'unfulfilled_lint_expectation' to plural)

r? `@ghost`
`@rustbot` modify labels: rollup
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants