amitr0
2007-03-22 03:24:38 UTC
I am working on a personal project where I just want to dump all the
data coming to the LSP (receive). So I use th Microsoft sample.
I had to fix the CopyWSABuf code so that a true copy of the buffer was
made on NT/2K systems. And FreeWSABuf to delete them too!
I have patched the WSPRecv code (Non over lapped case) to extract the
buffer. And I have patched the IntermediateCompletionRoutine Code RECV
part with same logic to tap the overlapped case.
I am facing an issue.
I ob serve that the LSP doesn't see all data transferred. I tested the
code with passing it a data file specially generated. It had
increasing DWORDS in it. So I know I am missiing some data.
The remarkable thing is if hte LSP is running attached to a debugger,
of if I use DbgMon to see the debug messages, I get the right file
with the DWORD pattern matching.
Why is that so???? Debuggers make machines slow. So does this have
something to do with timing????
any pointers on this???
data coming to the LSP (receive). So I use th Microsoft sample.
I had to fix the CopyWSABuf code so that a true copy of the buffer was
made on NT/2K systems. And FreeWSABuf to delete them too!
I have patched the WSPRecv code (Non over lapped case) to extract the
buffer. And I have patched the IntermediateCompletionRoutine Code RECV
part with same logic to tap the overlapped case.
I am facing an issue.
I ob serve that the LSP doesn't see all data transferred. I tested the
code with passing it a data file specially generated. It had
increasing DWORDS in it. So I know I am missiing some data.
The remarkable thing is if hte LSP is running attached to a debugger,
of if I use DbgMon to see the debug messages, I get the right file
with the DWORD pattern matching.
Why is that so???? Debuggers make machines slow. So does this have
something to do with timing????
any pointers on this???