how identify syscall number for non-exported syscall wrappers?

[derekbruening]

From [email protected] on May 06, 2011 15:52:50

some user32.dll and kernel32.dll syscall wrappers are not exported (NtWow64*, etc.: xref issue #384 ) so we need private syms to find them (or need to store a table of syscall nums by OS version). not all will have workarounds like issue #352 .

should have frontend look for kernel32 and user32 syscalls and download to
symbols/ dir inside drmem, w/ options to specify elsewhere or disable.
should use _NT_SYMBOL_PATH if already set.

alternatively maybe the table is the better solution: no reliance on network access, not perf hit on startup. won't work on new version of windows but we'll need to put in updates for that anyway.

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

[derekbruening]

From [email protected] on June 09, 2011 05:36:10

issue #446 proposes using a table here

[derekbruening]

From [email protected] on June 26, 2011 13:56:30

This issue was closed by revision r352 .

Status: Fixed