Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.

[Release/2.1] Respect profiler provided IL maps (Port #25802) #27295

Merged
merged 1 commit into from
Nov 22, 2019

Conversation

davmason
Copy link
Member

Description

When a profiler modifies IL it can also provide an updated source->IL map so that the debugger (or potentially any other consumer of the source->IL map) can correctly process the updated function. There was a type introduced in 2.1 that effectively makes the runtime ignore the profiler provided maps when the debugger asks for them.

Customer Impact

Debugging is broken for profiler modified functions, this was reported by a customer that uses the profiler APIs for a unit test framework.

Regression?

It is a regression from desktop behavior, and preventing the customer's profiler from working with apps targeting 2.1. Profiling was not supported on core before 2.1 so it is not technically a regression on core.

Risk

Very low risk, this code path is only used by the debugger/DAC and the fix is easy to reason about.

…entedCodeMap (dotnet#25802)

* Fix GetSequencePoints when profiler provides mapping via SetILInstrumentedCodeMap

* code review feedback
@davmason davmason added area-Diagnostics Servicing-consider Issue for next servicing release review labels Oct 18, 2019
@davmason davmason added this to the 2.1.x milestone Oct 18, 2019
@davmason davmason requested a review from noahfalk October 18, 2019 20:16
@davmason davmason self-assigned this Oct 18, 2019
@davmason davmason changed the title Port #25802 to 2.1 servicing [Release/2.1] Respect profiler provided IL maps (Port #25802) Oct 18, 2019
@maryamariyan
Copy link
Member

Thank you for your contribution. As announced in dotnet/coreclr#27549 this repository will be moving to dotnet/runtime on November 13. If you would like to continue working on this PR after this date, the easiest way to move the change to dotnet/runtime is:

  1. In your coreclr repository clone, create patch by running git format-patch origin
  2. In your runtime repository clone, apply the patch by running git apply --directory src/coreclr <path to the patch created in step 1>

@maryamariyan
Copy link
Member

Please ignore my previous comment. Since this PR is not targeting master branch, no action would be needed here. Thanks.

@jeffschwMSFT
Copy link
Member

We are currently waiting on positive acknowledgement from the customer that this fully addresses their issue. Thank you to everyone involved.

@davmason
Copy link
Member Author

davmason commented Nov 8, 2019

I received validation from the customer today that this fixes the issue he was seeing. It is ready for review now.

@leecow leecow modified the milestones: 2.1.x, 2.1.15 Nov 12, 2019
@leecow leecow added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Nov 12, 2019
@davmason davmason merged commit d36fefc into dotnet:release/2.1 Nov 22, 2019
Anipik pushed a commit that referenced this pull request Nov 22, 2019
* Update CoreClr, CoreFx to servicing-28207-04, servicing-28208-01, respectively (#27899)

* update branding for 2.1 (#27914)

* Fix GetSequencePoints when profiler provides mapping via SetILInstrumentedCodeMap (#27295)

Port #25802 to release/2.1

* Update ILAsmVersion.txt
mmitche pushed a commit that referenced this pull request Nov 25, 2019
* Update CoreClr, CoreFx to servicing-28207-04, servicing-28208-01, respectively (#27899)

* update branding for 2.1 (#27914)

* Fix GetSequencePoints when profiler provides mapping via SetILInstrumentedCodeMap (#27295)

Port #25802 to release/2.1

* Use MicrosoftSHA2 for DAC signing (#27933)

* Use MicrosoftSHA2 for DAC signing

* Fix DAC name
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Diagnostics Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants