Crash is not always due to the running trace

[GoogleCodeExporter]

When a crash is caused by a task running in background, it may occur after the 
trace that launched the task ended.
In this case, the crash is attributed to the task running at the moment of the 
occurrence.
This causes many problems:

1) a "good" trace is marked as crashed
2) a "bad" trace is marked as not failed
3) the good trace will not be explored further since it's supposed to crash
4) the bad trace will be explored further causing more (asynchronous) crashes 
and more unexplored (but actually good) branches

Original issue reported on code.google.com by nofatclips on 4 Dec 2011 at 9:44

[GoogleCodeExporter]

Workaround: allow resume with pause after 1 trace.
This way, each task execute on a "fresh" machine and should not suffer crashes 
due to previous tasks.
[Lowered priority]

Original comment by nofatclips on 16 Feb 2012 at 9:46

• Added labels: Priority-Low
• Removed labels: Priority-Medium