chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
0 votes
I've just upgraded to VS 2005 Team and have converted to using the integrated MS test tools. All my tests run fine when I run them. However, when I debug the tests I get errors whenever I step into the code under test.

Sometimes it's stack overflows, sometimes it's execution errors. But I can't step all the way through any test that uses TypeMock.

I've also disabled the code coverage option for the test configuration, but it didn't make any difference.

I was able to debug using VS 2003 with only the occasional problem.

Not sure how to get a debug log using the MS test runner?

------

FatalExecutionEngineError was detected
Message: The runtime has encountered a fatal error. The address of the error was at 0x7c81eb33, on thread 0x650. The error code is 0x800703e9. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.
asked by DaveL (1.7k points)

2 Answers

0 votes
Hi,
Please tell me what version of TypeMock you are using.
(You can see it from the TypeMock Configurator in the About tab)

If you add the following lines in a test you can find the location of the log file:
Console.WriteLine(System.Diagnostics.Process.GetCurrentProcess().MainModule.FileName);
MockManager.LogFile = true;

Can you please the typemock.out file.
answered by scott (32k points)
0 votes
I've reinstalled the latest and it's working again. I think that the version that was referenced by the test was different than the installed version!
answered by DaveL (1.7k points)
...