Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

handle system call failure: delay vs undo, races, etc. #119

Open
derekbruening opened this issue Nov 28, 2014 · 0 comments
Open

handle system call failure: delay vs undo, races, etc. #119

derekbruening opened this issue Nov 28, 2014 · 0 comments

Comments

@derekbruening
Copy link
Contributor

From derek.br...@gmail.com on December 10, 2010 17:57:47

PR 408540

on syscall failure:
/* FIXME: the shadow writes we enacted in event_pre_syscall() should be
* considered to have NOT happened. We can detect some with checks
* on known IN args that will cause failure (NULL, etc.).
* How handle races though? Xref all the discussion over malloc/free
* failure races, possibility of locking, and whether better to
* undo or delay.
*/

Original issue: http://code.google.com/p/drmemory/issues/detail?id=119

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant