Hermès Bélusca-Maïto e3a7066279 [CSRSRV] CsrCaptureArguments(): Tell the compiler the contents ClientCaptureBuffer points to has a volatile character. ... See https://docs.microsoft.com/fr-fr/archive/blogs/itgoestoeleven/why-your-user-mode-pointer-captures-are-probably-broken for more details. Since the contents of ClientCaptureBuffer is in the shared memory, the client could modify it while it is being probed and captured, and so we have to avoid any potential compiler optimizations regarding the captured "Length = ClientCaptureBuffer->Size" and "PointerCount = ClientCaptureBuffer->PointerCount" values.		2020-04-15 14:14:06 +02:00
..
api.c	[CSRSRV] CsrCaptureArguments(): Tell the compiler the contents ClientCaptureBuffer points to has a volatile character.	2020-04-15 14:14:06 +02:00
api.h
CMakeLists.txt	[CMAKE] Use modules instead of shared libraries	2019-04-06 17:43:38 +02:00
csrsrv.rc
csrsrv.spec
init.c
procsup.c	[CSRSRV] Only when CSRSRV is compiled in debugging mode, should we display debugging messages and support debug breakpoints.	2020-04-15 02:06:58 +02:00
server.c	[CSRSRV] Protect the Server DLL entrypoint calls under SEH.	2020-04-15 02:06:58 +02:00
session.c
srv.h
status.h
thredsup.c
wait.c