How to Terminate a CWinThread

[Bob Stanneveld]

Hello, I think that you have a worker thread problem. Read here[^] about threads. As stated in the article, you can kill your thread by calling ::TerminateThead((HANDLE)_YourWinThreadObject_);, but this is not safe, since your resources will not be cleaned up nicely... Behind every great black man...             ... is the police. - Conspiracy brother Blog[^]

[ThatsAlok]

could you show me your coding of OnInitDialog Function?

"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow

cheers, Alok Gupta

[a_du]

en. Thanx. i try it now.

[Nilesh K]

Simpler way out could be checking a flag in your thread's loop and this flag be changed by your application before exiting.

- Nilesh "Reading made Don Quixote a gentleman. Believing what he read made him mad" -George Bernard Shaw

[a_du]

Using Pointer really can change access the data have been passed into the thread. thanx a lot. One more question is that is there any potential problem if uing this method. i mean , if the thread loop is reading the status while outside fuction change the status at same time.

[Cedric Moonen]

Yes, there can be problems so it is better to use a CCriticalSection for both reading and writing to the variable. Take a look at the MSDN doc, it is not really complicated to use. If you have any further questions, don't hesitate to ask.

[pierrekande]

There is several way to terminate your thread. Let me suppose that you understand about synchronisation. And also to make thing more easier, define a static member variable of type: static BOOL m_endLoop for your dialog class CYourDLG; and also define a static member of type: static CEvent m_EventExit for your dialog class CYourDLG. in the CYourDLG::OnInit() function initialize m_endLoop=0; and call m_EventExit.SetEvent(). And in your function OnCancel and OnOk at before to exit, call WaitForSingleObject(EventExit,INFINITE); and in the first line in those 2 functions set m_endLoop =TRUE; and now in your loop function that terminate the thread, inside the loop insert this code: if(CYourDLG::m_endLoop==TRUE) { // first to some cleaning and close all opened file or whatelse ........... //and call CYourDLG::m_EventExit.SetEvent(); return 0; } ================== BUT when your start the thread insert this line at the begin of the thread function CYourDLG::m_EventExit.ResetEvent(); That is. You will have no access violation. This solution must help. Let me know if you have more questions Perre Kande

[David Crow]

See here for termination methods.

---

"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown

[David Crow]

a_du wrote: Actually i am not sur How can you not know? You call AfxBeginThread() in one of two ways. One way creates a worker (has no message pump) thread. The other creates a UI (has a message pump) thread.

---

"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown

[a_du]

:-DThank you very much. I have fixed my problem. I have a question about the GetExitCodeThread function. if AfxEndThread fucntion is called inside my thread, what value i can get use GetExitCodeThread function. dose AfxEndThread function really can deallocate all stack of hold by the thread. Thank you.