Communication from controller thread to worker thread

I have created a SDI class in my Visual C++ Studio 5.0.  Under the View class, I have begun a worker thread called worker() by using AfxBeginThread().  Also, I have passed the pointer to the View class for the worker thread to pass the messages to controller thread.  However, if I would like to kill the worker thread at any time, I do not know how to pass a message or control to kill worker().  EndThread() can only be executed in worker(), not outside the worker().  Besides, the worker() is only a function, not a class object.  It does not have its own message handle.  Anyway, is there any method for me to kill worker() once user click CANCEL button on CView's menu?  Thanks.
cw43Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

mnguyen021997Commented:
TerminateThread with the following precautions :

TerminateThread is used to cause a thread to exit. When this occurs, the target thread has no chance to execute any user-mode code and its initial stack is not deallocated. DLLs attached to the thread are not notified that the thread is terminating.

TerminateThread is a dangerous function that should only be used in the most extreme cases. You should call TerminateThread only if you know exactly what the target thread is doing, and you control all of the code that the target thread could possibly be running at the time of the termination. For example, TerminateThread can result in the following problems:

•If the target thread owns a critical section, the critical section will not be released. •If the target thread is executing certain kernel32 calls when it is terminated, the kernel32 state for the thread's process could be inconsistent. •If the target thread is manipulating the global state of a shared DLL, the state of the DLL could be destroyed, affecting other users of the DLL.



A thread cannot protect itself against TerminateThread, other than by controlling access to its handles. The thread handle returned by the CreateThread and CreateProcess functions has THREAD_TERMINATE access, so any caller holding one of these handles can terminate your thread.

If the target thread is the last thread of a process when this function is called, the thread's process is also terminated.

The state of the thread object becomes signaled, releasing any other threads that had been waiting for the thread to terminate. The thread's termination status changes from STILL_ACTIVE to the value of the dwExitCode parameter.

Terminating a thread does not necessarily remove the thread object from the system. A thread object is deleted when the last thread handle is closed.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
nietodCommented:
Most likely, a better method is to use a semaphore of some sort to instruct the thread to terminate.  This allows the thread to terminate in a safe way.
0
cw43Author Commented:
So, there is no way to communicate from controlling thread to worker thread?  In other words, if there are devices that I would like to release before I kill the worker thread, I have no way to control them, right?
0
mnguyen021997Commented:
it really depends on how immediate this kill needs to occur, also how your thread function is structured?  if your worker thread is in an infinite loop doing work it may be best just to have it check a flag at some point and time and terminate, so for instance:

threadfunc()
{
   for(;;)
   {
     if ( g_bDone )
       Exit();
     else
       DoSomeFunction();
     Sleep(100);
   }
}

where g_bDone can be set anywhere.  if you need critical section security then you can add it via any of the many blocking objects.  explain what your function does and we can better assist.  without a message loop you can't send/receive messages.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
C++

From novice to tech pro — start learning today.