[x86/Linux] Fix regdisplay initialization in case of WIN64EXCEPTIONS (dotnet/coreclr...
authorKonstantin Baladurin <k.baladurin@partner.samsung.com>
Tue, 3 Oct 2017 11:08:06 +0000 (14:08 +0300)
committerJan Vorlicek <janvorli@microsoft.com>
Tue, 3 Oct 2017 11:08:06 +0000 (13:08 +0200)
commit90e1ce7e26bbab0cc87cd20ef865e76a0a4726e6
tree24100e87f9ed624fd9d57ef3b4ae1d8121af60b5
parenta12ec894a13a8113ab25f54db70b1b692381f2ff
[x86/Linux] Fix regdisplay initialization in case of WIN64EXCEPTIONS (dotnet/coreclr#14296)

Method Debugger::IsThreadAtSafePlaceWorker for x86 sets values only
for ControlPC and PCTAddr fields of REGDISPLAY but there is assert
in StackFrameIterator::Init that checks that field pCurrentContext
is not NULL if WIN64EXCEPTIONS is defined.

This patch uses FillRegDisplay function to correctly initialize
regdisplay in case of WIN64EXCEPTIONS.

Commit migrated from https://github.com/dotnet/coreclr/commit/8eb9adbe7f069638c1457b458c2c5a569eaaabf8
src/coreclr/src/debug/ee/debugger.cpp