Problems with TI C/C++ Error Parser in Code Composer Studio v5.2.1 and v5.3.0

HI Arkadius,

would you  be able to send screen shots, ideally your project/a test case that reproduces this?  (That can be sent offline via a friend/conversation request).   Did you import the project  into the different versions?  Did you use a new workspace?  Have you tried clearing the metadata?

Best Regards,
Lisa

Hi Lisa,

thanks for your reply.

Today I have installed the newest CCS version 5.3.0.00090: the behaviour is the same as for the v5.3.0.00083, i.e., the TI error parser seems not to work. I deleted the metadata but it did not change the behavior. The original project files (.project and .cdtproject) were created for CCS 5.2.0.

I also added an own error parser to the CCS in order to compare it with the TI error parser.

Now the screenshots:

The attached file CCS_520_TI_ErrorParser.jpg contains the Console and the Problems view in CCS 5.2.0 (screenshot done on a different PC with Windows 7 Professional 32 bit, but the behavior was the same on the 64 bit PC): The TI C/C++ Error Parser works as expected (see e.g. the warning #552 in fft_example.c it is in the Console and the Problems view).

The second and third attachment will be added to the next posts since there is only one attachment per post allowed.

Best regards,

Arkadius

The second attachment CCS_530_TI_ErrorParser.jpg contains the screen shot of the Console and Problems view using the TI C/C++ Error Parser with CCS 5.3.0.00090: the warning is still in the Console view but it is not parsed correctly by the TI error parser, i.e there is no warning (or Info) in the Problems view.

The attachment CCS_530_user-defined_ErrorParser.jpg shows the Console and Problems view when using an own user-defined error parser with CCS 5.3.0.00090: this seems at least to find the warning (see again warning #552) and the infos but in the description of the warning in the Problems view is only the first line contained because the user-defined error parser seems to work only line by line and cannot have an error/warning/info description that spans multiple lines. Unfortunately the TI compiler always wraps the error/warning/info messages in the Console. If you compare this with the description produced by the TI error parser on CCS 5.2.0, you can see that the TI error parser has the whole warning description (corresponding to multiple lines in the Console) in the Problems view. It would be nice to have the TI error parser that was working with CCS 5.2.0 also working with CCS 5.3.0.

Hi Arkadius,

can we confirm a couple things.  You don't have supress warnings enabled?  Your other error parser is not interfering? 

I have so far not seen this with v5.3 so it would be good ot have any information which would help us reproduce the situation.  In face I was just working with a project with both errors and warnings being properly displayed.

Best Regards,
Lisa

Hi Lisa,

I do not suppress warnings or remarks (otherwise also my own error parser would not work). My error parser is located in the error parser list below the TI Error Parser and is also deactivated when testing the TI error parser (the TI error parser was even not working when my error parser did not exist).

In between I tested some "things" and actually found out when the TI error parser is not working or "partially" working (but I do not know why) in CCS 5.3.0 (but was working in CCS 5.2.0).

Configuration 1:

This is the current project configuration that is not working with CCS 5.3.0 (but was working with CCS 5.2.0): My makefile project is a CDT project (i.e. I have 3 project files: .project, .cproject and .cdtproject). The active error parsers are listed in the .project file, the active binary parsers in .cproject file. Here the first lines of the .project file:

<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
   <name>UMRR_2G</name>
   <comment></comment>
   <projects>
   </projects>
   <buildSpec>
      <buildCommand>
         <name>org.eclipse.cdt.make.core.makeBuilder</name>
         <triggers>clean,full,incremental,</triggers>
         <arguments>
            <dictionary>
               <key>org.eclipse.cdt.core.errorOutputParser</key>
    <value>com.ti.ccstudio.errorparser.CoffErrorParser;com.ti.ccstudio.errorparser.LinkErrorParser;com.ti.ccstudio.errorparser.AsmErrorParser;org.eclipse.cdt.core.GmakeErrorParser;</value>
</dictionary>

 The active error parser are listed in one line between <value> and </value> separated by semicolon (;). The "TI C/C++ Error Parser" is the first one: com.ti.ccstudio.errorparser.CoffErrorParser.

Configuration 2:

For test purposes I created a new makefile project as follows (in this configuration the TI error parser was working (almost as in CCS 5.2.0)):

In CCS: File-> New -> Project -> C Project [Nerxt] Makefile project -> Empty project  and selected my existing directory as location. In that case only 2 project files are created: .project and .cproject. The active error parser are listed this time in the .cproject (and not in .project as for Configuration 1). The active binary parser are also located in the .cproject file (the same as for Configuration 1). The first lines of the .cproject are as follows:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?fileVersion 4.0.0?>

<cproject storage_type_id="org.eclipse.cdt.core.XmlProjectDescriptionStorage">
   <storageModule moduleId="org.eclipse.cdt.core.settings">
      <cconfiguration id="0.329962028">
         <storageModule buildSystemId="org.eclipse.cdt.managedbuilder.core.configurationDataProvider" id="0.329962028" moduleId="org.eclipse.cdt.core.settings" name="Default">
            <externalSettings/>
            <extensions>
               <extension id="org.eclipse.cdt.core.ELF" point="org.eclipse.cdt.core.BinaryParser"/>
               <extension id="com.ti.ccstudio.binaryparser.CoffParser" point="org.eclipse.cdt.core.BinaryParser"/>
               <extension id="com.ti.ccstudio.errorparser.CoffErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
               <extension id="org.eclipse.cdt.core.GmakeErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
               <extension id="com.ti.ccstudio.errorparser.LinkErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
               <extension id="com.ti.ccstudio.errorparser.AsmErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
            </extensions>
         </storageModule>

The binary and error parsers are mixed in one list between <extensions> and </extensions> . The TI C/C++ Error Parser is the third one (com.ti.ccstudio.errorparser.CoffErrorParser).

Comparison of the configurations:

It seems that CDT makefile projects (Configuration 1) that were working in CCS v5.2.0 are not working properly in CCS v5.3.0 (with respect to the TI C/C++ error parser). There is no output in the Problems view.

When creating a new makefile project (no CDT project, see Configuration 2), the TI error parser works in CCS v5.3.0 but has one limitation or difference in comparison to the TI error parser in CCS v5.2.0:

• If the compiler (cl6x) is called without the -pdv option (Verbose diagnostics), the errors/warnings/remarks (in the Console view) are always without any line breaks and the TI error parser is working (the error/warning description in the Problems view is complete), i.e. it works in CCS v5.3.0 and v5.2.0 perfectly.
• If the compiler is called with the -pdv option, the errors/warnings/remarks contain usually line breaks (span multiple lines) and only the first line is included in the description field of the Problems view, i.e. the TI error parser is working "partially" in CCS v5.3.0. In CCS v5.2.0 the complete description of the error/warning was included in the Problems view (see the fille attached in the 3rd post: CCS_520_TI_ErrorParser.jpg).

A small example file (TestFile.c) for testing the -pdv compiler option:

#include <stdio.h>
void main()
{
   int  myLongTestVariable = 0;
}

Compiling this file (in CCS v5.3.0) with the -pdv option produces the following output in the Console view:

cl6x -pdv -pden -g -k -q -ss -mv6600 -o2 -fr obj -fs asm -ft obj TestFile.c
"TestFile.c", line 5: warning #179-D: variable "myLongTestVariable" was
          declared but never referenced
     int  myLongTestVariable = 0;
          ^

and the following description in the Problems view for CCS v5.3.0 (only the first line of the warning from the Console view is displayed):

#179-D: variable "myLongTestVariable" was

In CCS v5.2.0 the description in the Problems view was complete:

TestFile.c", line 5: warning #179-D: variable "myLongTestVariable" was declared but never referenced int  myLongTestVariable = 0; ^

Compiling this file without the -pdv option produces the following output in the Console view:

 cl6x -pden -g -k -q -ss -mv6600 -o2 -fr obj -fs asm -ft obj TestFile.c
"TestFile.c", line 5: warning #179-D: variable "myLongTestVariable" was declared but never referenced

and the following description in the Problems view for both CCS v5.3.0 and v5.2.0 (complete description since contained within one line in the Console view):

 #179-D: variable "myLongTestVariable" was declared but never referenced

Summary:

1. For CDT (makefile) projects in CCS v5.3.0 the "TI C/C++ Error Parser" is not working at all (no output in Problems view), maybe it is not called at all. It was working in CCS v5.2.0.
2. For makefile projects (without .cdtproject) and if the compiler option -pdv (Verbose diagnostics) is active (i.e., compiler error/warnig descriptions span, in general, multiple lines in the Console view), in CCS v5.3.0 only the first line is displayed in the decsription field of the Problems view. In CCS v5.2.0 all lines were displayed.
3. For makefile projects (without .cdtproject) and if the compiler option -pdv is not active (i.e., compiler error/warnig descriptions have no line breaks in the Console view), in CCS v5.3.0 the complete error/warning description (it is anyway only one line) is displayed in the decsription field of the Problems view. In CCS v5.2.0 it was the same.

Thus, only the option 3 is completely working in CCS v5.3.0 whereas in CCS v5.2.0 all above options were working. Thus, something has changed (with respect to the TI C/C++ Error Parser) between v5.2.0 and v5.3.0.

Could you at least confirm that you have the same behavior for 2 and 3, i.e., could you please compile your code with -pdv and without -pdv option and compare the description in the Problems view. Thanks.

It should be noted that I have only activated "C/C++ Problem" type in the "Configure Contents" settings of the Problems view in order to illustrate the "TI C/C++ Error Parser" problems. Other types (like "Semantic Error") are (in my opinion) not influenced by the "TI C/C++ Error Parser" (see the attached file CCS_Problems_view_configuration.jpg).

Best regards,

Arkadius