dangerous QThread

[Radagast]

If it is only ATTEMPT to corrupt memory, the main thread shouldn't be corrupted after the termination of the secondary thread afaik. The sec.thread has its own code and stack segments, OS clear them and then pass the control to the main thread, perhaps notifying it "oops I've just killed your child".
Anyway I've just discovered SEH exceptions, I suppose it will help.

What do you think, which errors may rise while reading corrupted binary file of complex structure (ints, floats, strings, bitmaps etc)?

[marcel]

What do you think, which errors may rise while reading corrupted binary file of complex structure (ints, floats, strings, bitmaps etc)?

mostly buffer overruns, but depends what/how you read... you could implement a completely safe file loader... all applications have mechanisms to detect corrupted files.
I just think you're trying to reinvent the wheel there.

[wysota]

If it is only ATTEMPT to corrupt memory, the main thread shouldn't be corrupted after the termination of the secondary thread afaik.

If there is at least one case when this is not true, then this whole statement is not true. And there is at least one case when this is not true, for instance when writing to an area of memory that is protected from write access - you might write some data and then reach the protected page/segment/area - the application did something that it shouldn't have and thus should be terminated.