You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SNIPER is an accurate, robust, and transparent tracing solution for Windows APIs.
SNIPER comes in two implementation variants. One builds on DBI (dynamic binary instrumentation) and another one for CPU virtualization extensions (Intel VT-x) that ships as an extension of the DRAKVUF analysis system, relying on its invisible breakpoints for out-of-guest instrumentation*.
(*) Unfortunately, the SNIPER extension for DRAKVUF relies on a dedicated DRAKVUF patch - patch-drakvuf-376c03d.diff
According to the roadmap of DRAKVUF, how DRAKVUF design and implementation should be enhanced to enable a future version of SNIPER that will no longer require a dedicated DRAKVUF patch ?
The text was updated successfully, but these errors were encountered:
I looked at the patch briefly and it looks like a good addition. It would still need to be cleaned up and ideally split into multiple PRs but I don't see a blocker for it being upstreamed.
SNIPER is an accurate, robust, and transparent tracing solution for Windows APIs.
SNIPER comes in two implementation variants. One builds on DBI (dynamic binary instrumentation) and another one for CPU virtualization extensions (Intel VT-x) that ships as an extension of the DRAKVUF analysis system, relying on its invisible breakpoints for out-of-guest instrumentation*.
(*) Unfortunately, the SNIPER extension for DRAKVUF relies on a dedicated DRAKVUF patch -
patch-drakvuf-376c03d.diff
According to the roadmap of DRAKVUF, how DRAKVUF design and implementation should be enhanced to enable a future version of SNIPER that will no longer require a dedicated DRAKVUF patch ?
The text was updated successfully, but these errors were encountered: