here is an excerpt from MSDN:
"Be careful when using setjmp and longjmp in C++ programs. Because these functions do not support C++ object semantics, it is safer to use the C++ exception-handling mechanism."
it seems that local objects are not destroyed properly
and Thread class does make use of longjmp()
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
here is an excerpt from MSDN:
"Be careful when using setjmp and longjmp in C++ programs. Because these functions do not support C++ object semantics, it is safer to use the C++ exception-handling mechanism."
it seems that local objects are not destroyed properly
and Thread class does make use of longjmp()
Thread makes use of longjump only to handle the one special situation where a thread is exited from it's Run method by calling Exit() implicitly.