DynamoRIO / DynamoRIO/dynamorio
events tests fail in CI build b/c sysnum not statically known
Open
Component-Tests
Migrated
OpSys-Windows
Priority-Medium
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 629
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 31
Description
_From [bruen...@google.com](https://code.google.com/u/109494838902877177630/) on December 08, 2010 13:37:41_
On Wed, Nov 10, 2010 at 02:19:57PM -0500, Zhao Qin wrote:
> The reason the filter_syscall_event is not called is because the system call
> number is not able to statically be determined. The code to execute the
> system call is:
>
> ntdll!KiFastSystemCall:
> mov edx, esp
> sysenter
>
> DR cannot determine the static system call number, so filter_syscall_event
> is not called.
Hmmm, unintended side effect of disabling -indcall2direct for -code_api.
_Original issue: http://code.google.com/p/dynamorio/issues/detail?id=365_
Contributor guide
Assessment
This issue has not been assessed yet.