[Google] Additional crash recording criteria

[Fitblip]

What steps will reproduce the problem?

1. If an application crashes or bails and pydbg doesn't catch the exception
   for some reason, the crash isn't recorded.
2. Right now this can be replicated with applications that throw C++
   exceptions, as pydbg doesn't seem to handle them properly.

What is the expected output? What do you see instead?
If the debugger thread exits and has to reattach, this should be recorded
as a potential crash

What version of the product are you using? On what operating system?
My really hacked up version of sulley. :) on Ubuntu

Please provide any additional information below.
Once sulley calls post_send in process_monitor and before it calls
restart_target there should be logic that says:

If dbg.thread = dead && app.pid = gone.
    record.crash to session