#4 User Callbacks

[Christoph Schwarz]

User callbacks work in principle in all environments (win32, win64 and wow64). However, the following issues are still unresolved:

1. WOW64 has no way to determine the size of the CAPTUREBUF. A solution needs to be found how to determine this size for all possible user callbacks
2. Valgrind does currently not care much about the contents of the CAPTUREBUF. However, there might be pointers to memory initialized by the kernel. It must be investigated which memory regions and processor registers to mark as "initialized" in a user callback. This might require detailed knowledge about the contents of the CAPTUREBUF for each user callback

The source of the ReactOS project might be useful (they must have implemented user callbacks).

All findings should be documented under [CallbacksFromSystemCalls].

[Christoph Schwarz]

• Description has changed:

Diff:

--- old
+++ new
@@ -1,7 +1,7 @@
 User callbacks work in principle in all environments (win32, win64 and wow64). However, the following issues are still unresolved:


 1. WOW64 has no way to determine the size of the CAPTUREBUF. A solution needs to be found how to determine this size for all possible user callbacks
-2. Valgrind does currently not care much about the contents of the CAPTUREBUF. However, there might be pointers to memory initialized by the kernel. It must be investigated which memory regions to mark as "initialized" in a user callback. This might require detailed knowledge about the contents of the CAPTUREBUF for each user callback
+2. Valgrind does currently not care much about the contents of the CAPTUREBUF. However, there might be pointers to memory initialized by the kernel. It must be investigated which memory regions and processor registers to mark as "initialized" in a user callback. This might require detailed knowledge about the contents of the CAPTUREBUF for each user callback

 The source of the ReactOS project might be useful (they must have implemented user callbacks).