Open gregg-miskelly opened 10 months ago
Visual Studio 17.8 string truncation behavior: in 17.7 and all previous releases, the debugger would attempt to read the entire value for any string variable. This would result in either the entire string being read, or the string being so large that it causes the debugger to crash with an out of memory exception. In 17.8, we now have caps when using DkmClrValue.EvaluateToString
or other APIs that inspect strings.
DkmEvaluationFlags.IncreaseMaxStringSize
, 5,242,880 characters or 10 megabytes can be readDkmClrValue
for strings might be impacted. See Rosyln PR 68969 for an example of using the new flags.
I am creating this issue as a place to announce breaking changes to the Concord API that might impact extension authors. To try and keep this to just announcements, I am going to lock this thread. But feel free to open issues in this repo if the instructions are unclear.