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

Jump to bottom

check for and handle syscall failure in all intercepted syscalls #148

Open
derekbruening opened this issue Nov 27, 2014 · 1 comment
Open

check for and handle syscall failure in all intercepted syscalls #148

derekbruening opened this issue Nov 27, 2014 · 1 comment
Labels
Migrated Priority-Low

Comments

@derekbruening
Copy link
Contributor

From derek.br...@gmail.com on May 28, 2009 10:00:33

while we do handle failure in the various mmap/mprotect syscalls we don't
for signal-related syscalls like SYS_rt_sigaction and SYS_rt_sigprocmask.
this Issue covers going through all of the intercepted syscalls and making
sure we're checking for and properly handling failure.

Original issue: http://code.google.com/p/dynamorio/issues/detail?id=148
@derekbruening
Copy link
Contributor Author

From bruen...@google.com on June 02, 2013 19:44:31

expanding this to cover Windows, including NtProtectVirtualMemory and NtAllocateVirtualMemory (from issue #1175 )

Owner: ---
Labels: -OpSys-Linux

@groleo groleo mentioned this issue Dec 17, 2014
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Migrated Priority-Low
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@derekbruening