[staleness] monitor syscall params for staleness

_From [derek.br...@gmail.com](https://code.google.com/u/117968039472581148324/) on December 10, 2010 19:52:17_

PR 553718

For completeness should mark as accessed all kernel reads and writes of
syscall params. For kernel-written, prob app will read some part of that
malloc, but can have kernel-read data show up as stale when not.

Impl plan is to link in all syscall*.c files, and eliminate logfile hashtable
since would then be a dup.
Also need alloc_drmem.c signal and callback handling and need
client_per_thread_t fields: which means need drmem's across-callback
scheme w/ filepos explicitly copied.
For handling unknown syscalls: also need client_per_thread_t fields =>
see above.

_Original issue: http://code.google.com/p/drmemory/issues/detail?id=221_