The parameter(s) passed to the server in the client/server shared memory window were invalid. Too much data may have been put in the shared memory window.
This is probably not the correct interpretation of this error.
The Win32 error above is more likely to indicate the actual problem.
Flags
Severity
Success
This code indicates success, rather than an error.
This may not be the correct interpretation of this code,
or possibly the program is handling errors incorrectly.
I'm trying to do a buffer overflow like it was described here, and I couldn't find the offset of the return pointer until I brute forced it, and I found it to be 21. Following this stackoverflow post, I got the following memory dump: (gdb) r 21 The program being [...] read more
I am trying to identify memory leak in a process(C++ Application) I am using Windbg tool to identify the memory leak. 0:000> !heap -stat -h 02e10000 heap @ 02e10000 group-by: TOTSIZE max-display: 20 size #blocks total ( %) (percent of total busy bytes) 40 95857 - 25615c0 (60.70) 953130 1 [...] read more