windows - MFC: troubleshooting on which thread is responsible for causing a crash -


I currently have two separate threads running for my project (for an MFC operation, such as view / projection, application Window etc.) and for an infinite, while loop in its main function). However, for some situations, when I run my program in debug mode, I have found that the 'exit status' of threads was 1 (in other words, this was returned non-zero numbers to the operating system). When applying in Visual Studio 2005, what would be the easiest way to figure out which thread is responsible for the return value, so that I can get rid of what is going on? thank you in advanced.

Including the suggestion of Steve Gilham:

After checking the detective ++, which thread is responsible for error, after checking, I have a line of HDL Unit Device () call Pinched is responsible for this return message by the Novvant Falcon SDK. Returning the failure status with this call does not cause any error message to pop up, however, I do not know that this is a big deal that is necessary to deal with a larger context. Thanks for listening to this suggestion would be great.

How is subdued thread used? My first thought is that if it is being closed in a non-fashionable fashion while leaving the main thread, then it can be a cause of zero-zero condition.

At the very least, if you can reduce that time when the two ends thread, then it can tell which situation is returning.


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -