Debug Visual C++ memory allocation problems

Question

I\'m debugging a software which crashes eventually with one of the following messages:

1. DAMAGE: after normal block (#24729280) at 0x00D710E0
2. Debug Assertion         


        

Answer 1

You can run your application in release mode by attaching to Windbg.

• Enable the gflags ( As you mentioned)
• Start the application in release mode.
• Attach it to Windbg using Attach to process option in Windbg.
• Configure the correct path for release PDBs.
• Reload the PDB manually using .reload /f in case of automatic loading fails.
• Perform the use case.

WinDbg would stop the execution whenever an exception occurs. For every first chance exception, analyze the reasons. It could be one of the error for crash.

Answer 2

Before using gFlags/PageHeap I suggest you to check for Access Violation exception. First attach the process by using Build->Start Debug->Attach to process option. Once it is attached enable the access violation exception by going to Debug->Exceptions select Access Violation and select the check box Stop Always. Then check whether your debugger catches any access violation exceptions.