This topic describes some of the common problems encountered in
collecting performance data. To correct the Collector configuration, you
must disable the Collector first, by choosing
Debug Performance Toolkit
Disable Collector. Then enable the
collector again and change the configuration. If you do not disable the
Collector after making a mistake, the last valid configuration is used
when you run your program.
You must have a program loaded into the Debugger before you can enable the Collector.
Experiment names must end in .er. If the experiment already exists the Collector does not overwrite it.
Experiment group names must end in .erg. You must also ensure that the group name does not include the path, because the experiment directory is inserted at the beginning of the group name.
The Collector does not overwrite existing experiments. Instead it increments the number n in the experiment name stem.n.er until it finds an unused name.
The profiling interval is rounded to a multiple of the system clock resolution. If it is smaller, it is rounded up; if it is larger, it is rounded down to the nearest multiple.
You must choose counters that count on different registers. Click Show for a list of hardware counters, and check the register number for the counters you have chosen.
If the hardware counter overflow profiling section of the Collector window is dimmed, hardware counter overflow profiling is not available on the computer you are using.
You must select Other from the Counter Name combo box to activate the Show button.
This feature is not available from the Collector window. To disable samples recorded when dbx stops the process, use the Debugger Console tab in the Output Window to enter the command collector dbxsample off.
See also | |
---|---|
Experiment Names Choosing a Value For the Profiling Interval Hardware Counter Data |