Windows error 0x00000255, 597

Detailed Error Information

CLIENT_SERVER_PARAMETERS_INVALID^[1]

Message	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.
Declared in	winerror.h

This appears to be a raw Win32 error. More information may be available in error 0x80070255.

HRESULT analysis^[2]

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.
	Reserved (R)	false
	Origin	Microsoft
	NTSTATUS	false
	Reserved (X)	false
Facility	Code	0 (0x000)
	Name	FACILITY_NULL^[2]^[1]
	Description	The default facility code.^[2]^[1]
Error Code		597 (0x0255)

Questions

Why is this the offset of the return pointer? "smashing the stack"

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

gdb

disassembly

buffer-overflow

Explain if any memory leak associated with oleaut32!APP_DATA::AllocCachedMem and ntdll!RtlAllocateHeap in windbg stack trace which appears repeatedly

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

c++

memory-leaks

Comments

Sources

winerror.h from Windows SDK 10.0.14393.0
https://msdn.microsoft.com/en-us/library/cc231198.aspx

User contributions licensed under CC BY-SA 3.0