Windows error 0x00000152, 338

Detailed Error Information

FT_WRITE_FAILURE^[1]

Message	The specified data could not be written to any of the copies.
Declared in	winerror.h

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

INVALID_PUSH_LOCK_FLAGS^[2]

This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0x152: INVALID_PUSH_LOCK_FLAGS.

HRESULT analysis^[3]

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^[3]^[1]
	Description	The default facility code.^[3]^[1]
Error Code		338 (0x0152)

Questions

Trouble displaying C# stack trace in WinDbg

I have a handle leak in a C# program. I'm trying to diagnose it using WinDbg using !htrace, roughly as presented in this answer, but when I run !htrace -diff in WinDbg I'm presented with stack traces that don't show the names of my C# functions (or even my .net [...] read more

windbg

stack-trace

handle-leak

gcc does not produce debugging symbols for local variable-length arrays (or gdb doesn't find them)

Apparently gdb cannot find the symbols associated with local variable-length arrays. Is it a gcc problem or a gdb problem? (Or maybe it's just my problem...). Take the following program "main.c" #include <stdio.h> #include <stdlib.h> int main( int argc, char **argv ) { int n; n = random() & 0xf; [...] read more

gcc

Comments

Sources

winerror.h from Windows SDK 10.0.14393.0
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
https://msdn.microsoft.com/en-us/library/cc231198.aspx

User contributions licensed under CC BY-SA 3.0