Skip to content

Handle 32-bit CLRDATA_ADDRESS semantics in ReadMemory - #1280

Merged
sdmaclea merged 2 commits into
dotnet:masterfrom
sdmaclea:CLRDATA_ADDRESS_32BIT
Jun 24, 2020
Merged

sdmaclea merged 2 commits into
dotnet:masterfrom
sdmaclea:CLRDATA_ADDRESS_32BIT

Conversation

@sdmaclea

Copy link
Copy Markdown
Contributor

This is at least an interim fix until microsoft/clrmd#774 is fixed.

/cc @leculver @hoyosjs

@sdmaclea sdmaclea added this to the 5.0 milestone Jun 23, 2020
@sdmaclea
sdmaclea requested a review from mikem8361 June 23, 2020 19:16
@sdmaclea sdmaclea self-assigned this Jun 23, 2020
@leculver

Copy link
Copy Markdown
Contributor

I'll have a nuget package out later today with steve's spot fix. I suggest not working around the issue and just picking up the fix.

@leculver

Copy link
Copy Markdown
Contributor

Fix shipped here: https://www.nuget.org/packages/Microsoft.Diagnostics.Runtime/1.1.132302.

@sdmaclea
sdmaclea merged commit b614b8c into dotnet:master Jun 24, 2020
@sdmaclea
sdmaclea deleted the CLRDATA_ADDRESS_32BIT branch June 24, 2020 16:51
sdmaclea added a commit to sdmaclea/diagnostics that referenced this pull request Jun 26, 2020
* Handle 32-bit CLRDATA_ADDRESS semantics in ReadMemory

* Use clrMD 1.1.132302
sdmaclea added a commit that referenced this pull request Jun 26, 2020
* Handle 32-bit CLRDATA_ADDRESS semantics in ReadMemory

* Use clrMD 1.1.132302
@github-actions github-actions Bot locked and limited conversation to collaborators Jan 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants