I have a particular test which crashes the ncrunch process nCrunch.TestHost.x86.exe to terminate with exit code 3. Is there any documentation on what different exit codes mean?
I have a particular test which crashes the ncrunch process nCrunch.TestHost.x86.exe to terminate with exit code 3. Is there any documentation on what different exit codes mean?
Remco NCrunch Developer
#4659
28 Sep 2013 12:56 UTC
Hi Rattle -
NCrunch tries to handle every exception it can, with the intention of reporting more detailed information as part of the test result. Because of this, any exit codes returned from the testhost process are indicative of a system error that NCrunch isn't able to handle or accurately report... so I'm afraid that error code 3 is unknown to me. I recommend trying to run the offending test with a debugger attached to see if this will give you more information.
Two common errors that are known to crash the testhost process in a way NCrunch cannot control are:
- Stack overflow
- Out of memory
NCrunch tries to handle every exception it can, with the intention of reporting more detailed information as part of the test result. Because of this, any exit codes returned from the testhost process are indicative of a system error that NCrunch isn't able to handle or accurately report... so I'm afraid that error code 3 is unknown to me. I recommend trying to run the offending test with a debugger attached to see if this will give you more information.
Two common errors that are known to crash the testhost process in a way NCrunch cannot control are:
- Stack overflow
- Out of memory
Thanks, the offending code caused a stack overflow error. I had tried to run in debug mode but that crashed out silently too.
Remco NCrunch Developer
#4663
28 Sep 2013 22:25 UTC
Great to hear you isolated the issue. NCrunch V2 is expected to bring improved handling of stack overflows. It's a tricky area, as a stack overflow generally causes the CLR to completely annihilate the process with no chance of recovery.
Post a reply
Log in to reply.