Odd behaviour of thread

[Silverlan]

I seem to be having a rather odd issue with threads. Maybe I still don't quite understand how they work, but this problem doesn't seem to make much sense at all.
Here's a simple recreation of my problem:

Code: [Select]

#include <SFML/System.hpp>
#include <iostream>

class TestThread : public sf::Thread
{
private :
    virtual void Run()
    {
while(true)
{
std::cout << "Sub thread..." << std::endl;
sf::Sleep(0.1f);
}
    }
};

void CreateThread()
{
    TestThread thread;
    thread.Launch();

while(true)
{
std::cout << "Main thread..." << std::endl;
sf::Sleep(0.1f);
}
}


int main()
{
CreateThread();
    return EXIT_SUCCESS;
}

This program works exactly as I want it to, both the main thread and sub thread are running at the same time and print a message into the console respectively.
However strange things happen if I change the main and CreateThread functions to this:

Code: [Select]

void CreateThread()
{
    TestThread thread;
    thread.Launch();
}


int main()
{
CreateThread();
while(true)
{
std::cout << "Main thread..." << std::endl;
sf::Sleep(0.1f);
}
    return EXIT_SUCCESS;
}
All I did was remove the infinite loop from CreateThread and paste it into the main function after CreateThread is called.
I would think that this should do exactly the same as it did before, both threads should run at the same time, and the messages should both be printed into the console. This is, however, not the case.
Instead it completely ignores the newly created thread and only the main thread seems to keep running.
Why is that? What am I doing wrong?
Any help would be really appreciated.

I'm using SFML v1.6 if that makes any difference.

[Drektar]

void CreateThread()
{
    TestThread thread;
    thread.Launch();
}

thread is destroy at the end of the CreateThread function so he don't have enough time to start.

If you do :

Code: [Select]

void CreateThread()
{
    TestThread *thread = new TestThread();
    thread->Launch();
}
It suppose to work but how you will delete the thread?

[Groogy]

You can have the thread delete itself when it's finished, though then that's a task model for your threading.

Anyway just make your thread object global or anything that will make it persist until not needed anymore. Also if you don't create more threads dynamically throughout the program but only at the start you can dynamically allocate memory(new) and forget about deleting them. When your application exits the OS will free any remaining memory for you. I know it's called bad programming but it is practical.

[blizter]

I had this problem and Drektar solution fixed it.

The created thread was running but not threaded. Weird.