linux windows thread differences

[anda_skoa]

You could put a log output in each thread's constructor, or set a break point in QObject::setParent() at the place where it warns about this.

The usual way to handle this is to check where you threads construct objects with a parent.

Cheers,
_

[marcofuics]

This is the correct way to reach the solution... but im a little bit confused: why the same program on linux goes well whilst in win32 crashes (saying about these problems)

[yeye_olive]

This is the correct way to reach the solution... but im a little bit confused: why the same program on linux goes well whilst in win32 crashes (saying about these problems)

There could be several reasons.
Do you manipulate all threads explicitly or do you user higher-level APIs like QtConcurrent which assign computations to threads in a manner that depends on the runtime environment?
Does the existence of parent-child relationships between QObjects in distinct threads depend on the scheduling of your threads?

You should review every creation of a QObject-derived object and make sure the parent (if any) lives in the thread that creates the child.

[anda_skoa]

This is the correct way to reach the solution... but im a little bit confused: why the same program on linux goes well whilst in win32 crashes (saying about these problems)

You should also get the warnings on Linux, but whether something crashes can depend on a lot of things, especially when threads are involved.

Cheers,
_