Debug Assertion Failed! _CrtIsValidHeapPointer( pUserData)
-
Hi, I have a Win32 Console Application which is throwing the Debug Assertion Failed! .. _CrtIsValidHeapPointer( pUserData ) and followed by a Debug Assertion Failed! .. _BLOCK_TYPE_IS_VALID(pHead->nBlockUse). After I did a Step by Step Debug strangely what I saw was it is throwing error once it is exittin the main function. Unlike any character pointers and deletion of heap without its references as of when generally this error occurs I have no such instances. please could you suggest a probable solution to this. please help.
There are only two kinds of people who are really fascinating-people who know absolutely everything, and people who know absolutely nothing. Oscar Wilde (1854-1900) Regards... Shouvik
-
Hi, I have a Win32 Console Application which is throwing the Debug Assertion Failed! .. _CrtIsValidHeapPointer( pUserData ) and followed by a Debug Assertion Failed! .. _BLOCK_TYPE_IS_VALID(pHead->nBlockUse). After I did a Step by Step Debug strangely what I saw was it is throwing error once it is exittin the main function. Unlike any character pointers and deletion of heap without its references as of when generally this error occurs I have no such instances. please could you suggest a probable solution to this. please help.
There are only two kinds of people who are really fascinating-people who know absolutely everything, and people who know absolutely nothing. Oscar Wilde (1854-1900) Regards... Shouvik
Looks like you are trying to delete the same pointer twice, or trying to delete something which is not a pointer to a heap based object. If you can post some of the code, then we can help.
Jonathan Wilkes Darka [Xanya.net]
-
Hi, I have a Win32 Console Application which is throwing the Debug Assertion Failed! .. _CrtIsValidHeapPointer( pUserData ) and followed by a Debug Assertion Failed! .. _BLOCK_TYPE_IS_VALID(pHead->nBlockUse). After I did a Step by Step Debug strangely what I saw was it is throwing error once it is exittin the main function. Unlike any character pointers and deletion of heap without its references as of when generally this error occurs I have no such instances. please could you suggest a probable solution to this. please help.
There are only two kinds of people who are really fascinating-people who know absolutely everything, and people who know absolutely nothing. Oscar Wilde (1854-1900) Regards... Shouvik
The normal debug configuration of a VS C++ project checks the heap hasn't been corrupted when you exit. If these assertions fire, the heap has been corrupted. This is a wild-write bug. Somewhere, you're using a bad pointer, or have made a mistake in pointer calculation, or allocated too little space for a buffer, or written off the end of a buffer. These are very hard to track down. Ensure that you always initialize pointers to NULL or to a real value, so you don't get random stack garbage that could point anywhere. If it's consistently the same address, you can use a data breakpoint to see when the data at that address changes. See 'data breakpoints' in MSDN Library.
Stability. What an interesting concept. -- Chris Maunder
-
Hi, I have a Win32 Console Application which is throwing the Debug Assertion Failed! .. _CrtIsValidHeapPointer( pUserData ) and followed by a Debug Assertion Failed! .. _BLOCK_TYPE_IS_VALID(pHead->nBlockUse). After I did a Step by Step Debug strangely what I saw was it is throwing error once it is exittin the main function. Unlike any character pointers and deletion of heap without its references as of when generally this error occurs I have no such instances. please could you suggest a probable solution to this. please help.
There are only two kinds of people who are really fascinating-people who know absolutely everything, and people who know absolutely nothing. Oscar Wilde (1854-1900) Regards... Shouvik
And maybe this tool will be helpful for you. Memory(-Leak) and Exception Trace (CRT and COM Leaks)[^]
WhiteSky
-
And maybe this tool will be helpful for you. Memory(-Leak) and Exception Trace (CRT and COM Leaks)[^]
WhiteSky
according to the following call stack
NTDLL! 7c901230() NTDLL! 7c96cd80() NTDLL! 7c960af8() KERNEL32! 7c85e9cf() _CrtIsValidHeapPointer(const void * 0x00032b78) line 1697 _free_dbg_lk(void * 0x00032b78, int 1) line 1044 + 9 bytes _free_dbg(void * 0x00032b78, int 1) line 1001 + 13 bytes operator delete(void * 0x00032b78) line 351 + 12 bytes CString::FreeData() line 146 + 15 bytes CString::~CString() line 213 $E155() + 34 bytes doexit(int 0, int 0, int 0) line 353 exit(int 0) line 279 + 13 bytes mainCRTStartup() line 345 KERNEL32! 7c816fd7()It is clear the error was occuring tryin to free the CString objects which incidentally I had made global due to the requirements. Hence I refactored my application and passed them as reference. What I inferred from the situation is that while tryin to free up the Cstring memory it encountered that the heap had already been unintiallized. however it is still unclear to me how was the heap cleared before even C Runtime tried to unregister it. I never explicitly have defined any destructors.
There are only two kinds of people who are really fascinating-people who know absolutely everything, and people who know absolutely nothing. Oscar Wilde (1854-1900) Regards... Shouvik