add client event for client or DR fault about dynamorio HOT 4 OPEN

From [email protected] on August 28, 2014 07:16:41

Owner: ---

from dynamorio.

From [email protected] on August 28, 2014 07:47:37

The challenge of invoking a client event callback on a fault inside DR
is that we do not know what to trust: we cannot easily tell whether it's
safe to acquire the lock for the event callback list, whether data
structures have been corrupted, or what.

from dynamorio.

Xref #1717

For non-DR crashes, so a crash in a client lib, it seems best to pass it to the client's fault handler if it registered one, so clients can handle faults in things like inlined memcpy or other client code and not just in gencode or the code cache. The risk is that the client's state is compromised and it hangs or messes up app state and we fail to get a good message to the user.

from dynamorio.

Xref #1470 on customized crash messages

from dynamorio.