
3. Type 0 for the address and click Go
4. In the Debug view, right-click on the top level node and choose
"Relaunch"
Workaround: Terminate your debug configuration first and then re-
launch it.
Warnings and errors when
the project name contain "-"
Projects with a dash (-) in their name may fail to build
To reproduce:
1. Install CCES, and create a project named TAR-48041, other
things set as default
2. Build the new created projects, there are warnings
3. Open the project Properties setting page, Enable MISRA-C
4. Rebuild the project, there is a error indicate the name should not
include "-"
Workaround: Do not use a dash in the name of your project.
Project paths that contain an
ampersand (&) will not build
If a project path has the ampersand character in it then it fails to
build.
To reproduce:
* Create a new project where the path to the project has a
ampersand in it.
* Build the project to see the error.
Workaround: Do not use ampersands in the path or project name.
String index out of range in
Debug As, Debug
Configuration menu
When there is more than one project open and you select a dxe to
run or debug, you may see a pop- up about 'String index is out of
range' and cannot load the dxe.
Workaround: To load the dxe, select to run or debug from the project
level instead of selecting the individual dxe.
"Invalid format:
STRING.Format" errors
when debugging
When debugging an executable you may occasionally see a number
of "Invalid format:
STRING.Format" errors in the output console and no application
output.
Workaround: None. This error can be safely ignored.
Not resolved errors in
system/uCLIB/source lib
files
When using the wizard to create a project that has uC/OS-III and
then clicking on the system/uCLIB/source files lib_ascii, lib_mem.c,
lib_math.c and lib_str.c files, you may see a number of errors in the
Problems window. These are spurious errors detected by the editor
Comentários a estes Manuais