1. re: NEW win32lib release_all_mem()
Matt, and Derek.
The patch you posted seems to have solved my GPF nightmare.
.. and Matt, here's a bit of Euman's debugger report I was referring to.
Overwrite detected on HeapAlloc block
* Corruption Detected *
Current location: HeapFree in WOTIDY7_FULL.EXE <see stack trace>
More info: Block address: LPVOID 1C22070h
Detailed Info: Overwrite condition detected on an allocated block
referenced in the HeapFree <see stack trace>.
The guard bytes of block 01C22070h, size 26, have been changed,
resulting in data and/or heap corruption.
The block was allocated by a HeapAlloc <see stack trace>
in module WOTIDY7_FULL.EXE.
To pinpoint the location of the actual corruption,
use BugCrusher mode or the mc_check_buffers() API.
Parameters:
hHeap is HANDLE 1B20000h (28442624)
Number of free blocks: 2
Number of used blocks: 42
Memory allocated in heap: 908 bytes
dwFlags is DWORD 0h (0)
lpMem is LPVOID 1C22070h (29499504)
Heap Block is USED
Size: 32
Stack Trace:
kernel32.DLL! HeapFree
WOTIDY7_FULL.EXE! ___CPPdebugHook + 4EAEh
WOTIDY7_FULL.EXE! __GetExceptDLLinfo + 69D80h
WOTIDY7_FULL.EXE! __GetExceptDLLinfo + 6AFF3h
WOTIDY7_FULL.EXE! __GetExceptDLLinfo + 62890h
WOTIDY7_FULL.EXE! __GetExceptDLLinfo + 62A48h
WOTIDY7_FULL.EXE! __GetExceptDLLinfo + 1D3E5h
Thread ID: FFF167C7h Prio: THREAD_PRIORITY_NORMAL (0)
More information about this resource:
Value: LPVOID 1C22070h (internal type: PHEAP_BLOCK_WIN)
Size: 1Ah (26) bytes
Block lies in a Windows heap.
Heap block status: USED Allocation #512
Allocated with HeapAlloc
* Free with HeapFree *
