Skip to content

Merge 'main' into 'release_mdd'#1609

Merged
WardenGnaw merged 4 commits into
release_mddfrom
main
Jul 10, 2026
Merged

Merge 'main' into 'release_mdd'#1609
WardenGnaw merged 4 commits into
release_mddfrom
main

Conversation

@WardenGnaw

Copy link
Copy Markdown
Member

No description provided.

gregg-miskelly and others added 4 commits June 30, 2026 13:12
- Add <Nullable>enable</Nullable> to MICore.csproj
- Add GlobalUsings.cs with NullableHelpers static import
- Add NullableAttributes.cs shared file
- Add nullable annotations (?) to all appropriate type declarations
- Add [NotNullWhen], [DoesNotReturn] attributes
- Add Debug.Assert statements for non-null invariants
- Replace string.IsNullOrEmpty/IsNullOrWhiteSpace with NullableHelpers versions
- Add using System.Diagnostics where needed for Debug class
- Remove redundant using aliases replaced by GlobalUsings

This also cleans up the code in `PipeTransport.ExecuteSyncCommand` as that code had the classic Process.Start deadlock
This PR fixes a race condition in Microsoft.DebugEngineHost.RegisteryMonitor where if `Stop` was called before the monitor thread started, it would never shutdown.

This fixes #1593
…1601)

Gate the memoryReference on pointer and array types in OpenDebugAD7

A non-pointer scalar shown in a data tip or the Variables view carried a
memoryReference, so VS Code rendered the "view binary data" icon and
navigated to an address equal to the value (hovering a uint32_t of 1
opened a memory view at 0x1).

The earlier approach gated AD7Property.GetMemoryContext in the engine, but
that method is shared with Visual Studio, where the Memory and Disassembly
windows resolve a typed address expression through it. Restricting it
there breaks entering a scalar or address expression into those windows.

Move the restriction to the DAP layer: in
AD7Utils.GetMemoryReferenceFromIDebugProperty, emit a memoryReference only
when the property type is a pointer or an array. GetMemoryContext is left
unchanged, so the Visual Studio memory and disassembly navigation keep
working, while VS Code no longer offers a memory view for scalars. VS Code
has no free-form address entry, so gating the reference removes no entry
point there.
@WardenGnaw WardenGnaw merged commit 3023626 into release_mdd Jul 10, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants