Currently if only one thread is suspended in the debugged process,
the resulting object of:
any InvokeMethod
ClassType.NewInstance
ArrayType.NewInstance
CreateString
commands may be garbage collected immediately. And even the subsequent DisableCollection command for such objects will already fail.
This leads to ugly workarounds like doing:
CreateString - DisableCollection
in a loop to get the new string mirror reliably.
That would be great to have a reliable solution for such cases.
the resulting object of:
any InvokeMethod
ClassType.NewInstance
ArrayType.NewInstance
CreateString
commands may be garbage collected immediately. And even the subsequent DisableCollection command for such objects will already fail.
This leads to ugly workarounds like doing:
CreateString - DisableCollection
in a loop to get the new string mirror reliably.
That would be great to have a reliable solution for such cases.