
Anomalies
The following table is a list of known anomalies in CrossCore Embedded Studio
1.0.0.
part function names in call
stack for C++ functions
When debugging an application, the displayed name for C++
functions in the call stack will not give all available information about
the functions. Information about namespace scope, templates, etc.
will be missing. For example, the function "my_test::array<short,
long>::array(int)" will be displayed as "array(int)". This issue may
make it difficult to navigate sources that use these standard C++
features
Symbol manager should
reset breakpoints when
memory initialization is
complete
If code that has breakpoints set in it is initialized using the runtime
initialization support, the instruction at the breakpoints will be
corrupted and the program will fail to execute properly. To avoid the
problem, do one of the following:
1) Disable run-time initialization support when you need to rely on
the use of breakpoints (for example, when debugging)
2) Ensure that code containing breakpoints is not initialized at
runtime. This can be done in one of two ways:
- by adding the following line to the the appropriate source file:
#pragma file_attr("requiredForROMBoot")
- By adding the function name (with a prefixed underscore) to the list
of functions defined in the LDF as
"OBJS_LIBS_WITH_BREAKPOINTS"
cldp crashes with
commands file that does not
have a new line at the end
When using a command file(-@ filename), the command line device
programmer will not work if the file does not have a new line at the
end.
Duplicate entries for HPUSB
emulator seen during Found
New Hardware Wizard
The USB device driver for the Analog Devices, Inc. line of emulators
inadvertently did not receive an update of its version. Therefore,
there may be times when installing the driver where the user may be
asked to pick between device drivers with the same exact version. It
is safe to choose the oem*.inf file where * is a higher number.
Memory Browser loses
memory tabs on relaunch
If you create a new memory tab in the Memory Browser view and
then re-launch your debug configuration using the "Relaunch" menu,
it loses the memory tab that you just created.
To reproduce:
1. Launch any debug configuration
2. Open the Memory Browser view
Comentarios a estos manuales