Hi there,
Sorry for the late reply, I've been a bit sick.
Today I compiled the code and put some breakpoints in there as you suggested on the points outlined here (on #1 and #2)
I also find it interesting that this behavior only occurs when running through vstest. When I run my workaround (load & execute a native DLL) there are no problems. Is it possible that the issue lies somewhere in the child-processes binding? Any way I can check this?
Or perhaps any other pointers where to look next?
Cheers,
Stefan.
Sorry for the late reply, I've been a bit sick.
Today I compiled the code and put some breakpoints in there as you suggested on the points outlined here (on #1 and #2)
auto it = addressLineMap_.find(address); // #1
if (it == addressLineMap_.end())
return boost::none;
auto& instruction = it->second; // #2
I can see that #1 is hit; to be exact, addressLineMap_ contains approximately 1 million breakpoints for my project. However, #1 is hit only 3 times, and #2 is never hit. During this time, I can see in the console window that the tests are being executed.I also find it interesting that this behavior only occurs when running through vstest. When I run my workaround (load & execute a native DLL) there are no problems. Is it possible that the issue lies somewhere in the child-processes binding? Any way I can check this?
Or perhaps any other pointers where to look next?
Cheers,
Stefan.









