BoundsChecker – Guidelines for Use
Contents
Item |
Notes |
|---|---|
1 |
BoundsChecker Configuration File •The configuration files are located where the executable that is to be analyzed is located. •Config file extensions are *.DPbcc or *.DPbcd (Default file extension). •For example, for the MxVDev sample program the config file is: C:\Program Files\MICROMAX\MxVDev\bin\ MxVDev.DPbcd |
2 |
When you change the C code or the BoundsChecker configuration: •Always stop/quit MxVDev. •Always rebuild all. |
3 |
You need: •Error Detection->General->LogEvents ON |
4 |
In Visual C++, from the Build on the main menu: •Select DevPartner Native C/C++ Instrumentation Manager … •Check the ‘Instrument …’ box •Select Error Detection •Check MxVDev |
5 |
For memory error (copy overrun) ensure the following: •Enable Memory Block Checking (under Call Validation) is enabled. |
6 |
Run-Time Error Detection Configuration •Analysis oGeneral – All off oData Collection - ? oDisplay – Don’t care oExclusions – Don’t care oExclusions – Don’t care oMerge – Ask oSession Control – Don’t care •Code Review – Don’t care •Error Detection oGeneral ▪Log Events – ON ▪Display error and pause – Causes a dialog box ▪Rest – Off oData Collection – Should be OK oAPI Call Reporting – Off oCall Validation - Enable ▪Memory Block – Enable ▪Fill Output Args – Enable ▪Rest – Off oCOM Call Reporting – Off oCom Object Tracking – Off oDeadlock analysis – Off oMemory Tracking – Enable all oNET Analysis – Off oNET Call reporting – Off oResource Tracking – Off oModules and Files – Just select SUT file oFonts and Colors – Don-t care oConfig File Mgmt – May be interesting |
7 |
Toolbar: •The first and ninth icons on the toolbar need to be selected, as shown below:
|
