add client event for client or DR fault #50
Comments
|
From bruen...@google.com on August 28, 2014 07:16:41 Owner: --- |
|
From bruen...@google.com on August 28, 2014 07:47:37 The challenge of invoking a client event callback on a fault inside DR |
|
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. |
|
Xref #1470 on customized crash messages |
From derek.br...@gmail.com on February 24, 2009 14:35:01
this was PR 200414
we'll want to add an event for faults occurring in DR or client code so that
a tool can report such failures in a customized way or try to recover from
client faults.
note we still don't have a good plan for SEH across client/DR boundary -
e.g. when a client passed a NULL pointer to a DR routine we'll currently
take the blame
we already provide dr_safe_{read,write}.
xref issue #51 /PR 198875 on adding try/except.
we already provide an exception event on Windows and a signal event on
Linux (PR 304708) for application faults (both of which do not handle
faults in DR or a client, deferring to this case).
Original issue: http://code.google.com/p/dynamorio/issues/detail?id=50
The text was updated successfully, but these errors were encountered: