As an experienced programmer, you may have already faced one of the hardest parts of your job: fixing a bug, such as an access violation, caused by corruption in program-allocated heap memory. Such bugs can be very difficult and frustrating to diagnose, because every change you make to the program also changes heap memory – including adding debug print code, commenting out code, running a debugger, and changing the input data. Thus, anything you do to investigate the problem may cause the symptom to disappear or move to another point in the program execution.
This Help system was created using a trial version of Adobe RoboHelp. Files generated with the trial version are intended for evaluation purposes only and may not be used or distributed for any other purpose.