Deleting the thread after completing the cycle [SOLVED]

[ONEEYEMAN]

Hi, ALL,
I'm following an example from the documentation for the detached thread.
Thread works fine, however problem arises when the application ends.

Here is the pseudo-code:

Code: Select all

wxThread::ExitCode Foo::Entry()
{
    std::vector<std::wstring> errorMsg;
    while( !TestDestroy() )
    {
// function call
    }
    return (wxThread::ExitCode) 0;
}

I did implement the thread deletion logic inside OnClose() as in the documentation. What I'd like to avoid is calling wxThread::Delete() in the middle of the "function_call". Something like this:

Code: Select all

wxThread::ExitCode Foo::Entry()
{
    std::vector<std::wstring> errorMsg;
    while( !TestDestroy() )
    {
        m_safeDelete = false;
// function call
        m_safeDelete = true;
        Sleep( 60 );
    }
    return (wxThread::ExitCode) 0;
}

I can make a member variable inside the thread class and check if its safe to delete the thread object and check if this flag is set as in the code above. But maybe such mechanism is already exists?

[doublemax]

I can make a member variable inside the thread class and check if its safe to delete the thread object and check if this flag is set as in the code above.

I don't see what difference that would make. If you call wxThread::Delete(), the thread doesn't get killed immediately. It only sets an internal flag which is checked with TestDestroy(). A detached thread will destroy (as in delete) itself when it terminates. (After you return from Entry()).

[ONEEYEMAN]

doublemax,
Maybe in this case I'm better off with the joinable thread? At least I will be in control when it will be deleted.

Thank you.

[doublemax]

Maybe in this case I'm better off with the joinable thread?

If the thread uses resources that could be deleted too early, that's an option.

[ONEEYEMAN]

doublemax,
No, it does not.
But with current code I have a not released pointer, because the call to Delete was executed in the middle of the some function call.
That's why I'd like to have a flag indicating that the function finished and its ok to delete the thread with Delete() call.

Now this function is a member of another class which is a member of my thread class. So its like this:

Code: Select all

class Foo : public wxThread
{
private:
    MyClass m_bar;
}

wxThread::ExitCode Foo::Entry()
{
    std::vector<std::wstring> errorMsg;
    while( !TestDestroy() )
    {
        m_bar->Bar( errorMsg );
    }
    return (wxThread::ExitCode) 0;
}

And so if the call to Delete() comes during the Bar() execution I will have a problem.

Thank you.

[doublemax]

And so if the call to Delete() comes during the Bar() execution I will have a problem.

Sorry, i still don't see why that's a problem. The Delete() call does not immediately kill the thread.

[ONEEYEMAN]

doublemax,
I don't know. I guess its just a timing issue.
But I think I might have a solution. I will do a clean-up in two places: when I don't need the resource and in the thread class destructor, making the resource a class member. That way everything should be good.

Thank you.