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
as part of the master plan we discussed a few years back, we'd like to take parts of drmem and turn them into extension libraries. so far we've done drwrap and drutil, and we've added drmgr to make them all cooperate well together.
this issue is about building the syscall parameter info as an extension library, "drsyscall" or "drsysparam". the API would likely look like the sysauxlib API I developed, though perhaps with some augmented type info for building strace-like tools.
unlike drwrap and drutil, drsyscall would likely stay within the drmemory code base
The preliminary DrSyscall release was completed back in Dec 2012. All missing features and extensions are filed as separate issues ( issue #1089 , issue #1093 , issue #1094 , issue #1092 , issue #1102 , issue #1106 , etc.). Closing this issue.
From [email protected] on March 09, 2012 09:36:12
as part of the master plan we discussed a few years back, we'd like to take parts of drmem and turn them into extension libraries. so far we've done drwrap and drutil, and we've added drmgr to make them all cooperate well together.
this issue is about building the syscall parameter info as an extension library, "drsyscall" or "drsysparam". the API would likely look like the sysauxlib API I developed, though perhaps with some augmented type info for building strace-like tools.
unlike drwrap and drutil, drsyscall would likely stay within the drmemory code base
Original issue: http://code.google.com/p/drmemory/issues/detail?id=822
The text was updated successfully, but these errors were encountered: