[mono] block debugger attach after managed ApplyUpdate is called

[lambdageek]

Block two scenarios:

1. managed ApplyUpdate is called with debugger attached
2. debugger tries to attach after managed ApplyUpdate is called.

The issue is that if updates and debugger state are out of sync, we don't have a mechanism to play the debugger up to the modified state so attaching would see outdated breakpoints, locals, etc. Revisit in future releases.

The only supported scenarios are:

• all updates come in through the debugger protocol
• all updates come from ApplyUpdate and the debugger never attaches

[ghost]

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Block two scenarios:

1. managed ApplyUpdate is called with debugger attached
2. debugger tries to attach after managed ApplyUpdate is called.

The issue is that if updates and debugger state are out of sync, we don't have a mechanism to play the debugger up to the modified state so attaching would see outdated breakpoints, locals, etc. Revisit in future releases.

The only supported scenarios are:

• all updates come in through the debugger protocol
• all updates come from ApplyUpdate and the debugger never attaches

Author:	lambdageek
Assignees:	-
Labels:	area-Diagnostics-coreclr, untriaged
Milestone:	-