How the debugger lied to my face with no shame at all

added by DotNetKicks
9/12/2016 8:07:26 PM


The real repro happened in a pretty complex piece of code, and because the old value was different than the value in the debugger, we were certain that we had something that was changing data behind our back. Only after we marked the memory as read only and still saw that behavior we realized that this is actually a debugger eval bug.