• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 57 subscribers
  • Views 1506 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS 4 error parser message presentation

Daniel Hissbach
Prodigy 20 points

Hello,

I'm using CCS 4.2.3.00004 with PC-Lint as a pre-build step.

After linting my code, the results were presented in the console view. Errors and warnings were passed to the problems tab. This works fine!

The presentation format of the lint messages is set, to fit the CCS error-parser requirements, so I can jump to corresponding code section.

 

Now my problem is, that I'd like to see the Info messages as well, but I'm not able to do this.

I already tried to set the filter options, that every message with severity level Error, Warning and Info should be shown.

 

Is the message format for Infos different, compared to errors and warnings?

Is it possible to show the Info messages?

 

Example for Warning (works fine):

#define SI32_MIN      ((SI_32)-2147483648)
"..\inc\L0\L0_StandardTypes.h", line 90: Warning: The type of
    constant '2147483648' (precision 32) is dialect dependent (PC-Lint Msg-No:
    694)

Example for Info ( doesn't work):

"..\inc\L0\L0_StandardTypes.h", line 91: Note: Violates MISRA
    2004 Required Rule 10.6, Unsigned integer literals require a 'U' suffix
    (PC-Lint Msg-No: 960)

 

Thank you.

 

 

  • 0
    TI__Guru**** 171004 points

    Hi,

    I don't think it is possible, unless you are able to elevate the Info category to errors in PC Lint itself - this could potentially redirect the info output to the stderr (where Eclipse would direct them to the problems tab) instead of stdout.

    Unfortunately I don't have PC Lint to try this myself.

    Regards,

    Rafael

  • 0 in reply to desouza
    Prodigy 20 points

    Hi,

    for explanation of the PC-Lint process:

    1.) PC-Lint is called with a list of files to check

    2.) output of PC-Lint is written to a (plain-) text-file

    3.) after linting the whole code, the text-file is written to stdout using the type command

     

    I copied the two messages mentioned above into a txt-file and ran  type name_of_file.txt as pre-build. So both messages were treated equally. This writes the content to the console view and the warning is passed to the problems tab.

    The headline in the problems tab summarizes the errors, warnings and infos. So I expect, that I could pass Infos to the problems tab.

    Is this feature working? What's the correct keyword?

    Is there any appnote/ information available?

     

    Regards,

    Daniel

     

     

     

  • 0 in reply to Daniel Hissbach
    Prodigy 10 points

    Hi Daniel,

    I am trying to do exactly the same thing as you.  I have reformatted the PC-Lint output so that Errors and Warnings are correctly picked up on the Problems tab.  However, it completely ignores Info messages from PC-Lint.  As an example, here is an example of a line that causes both a warning and info message to be output:

    if (reduce < loopIntergral) // TODO: Signed/unsigned mix in relational

    "C:\xxx\firmware\api_stuff.c", line 223: Warning: 574 Signed-unsigned mix with relational

    "C:\xxx\firmware\api_stuff.c", line 223: Info: 737 Loss of sign in promotion from int to unsigned int

    The Problems tab correctly shows all of the warning info in the proper columns, but completely ignores all Info: messages.  The Problems tab itself shows

    0 errors, 24 warnings, 0 infos

    Which makes me think that there must be some way to parse an Info line, but I (we) need to know what the magic keyword is.  Can someone from TI please help? 

    I can't even find a complete list of all possible error/warning/info messages so I could figure out how to format it myself.

    Thanks,

    Scott

  • 0 in reply to Scott Whitney
    Prodigy 20 points

    Did anyone have success with figuring out how to get something to output as "info" rather than a warning or error? 

    I am also tying in LINT and have a script that reformats the output so that errors and warnings show up correctly in the Problems tab but no success on the "info" items.  The other developers will balk at having items show up as errors or warnings (at least for now), so I was going to override them all to "info" at least until we have Lint issues under control.

    Any information on how to use or add to the Problems Filters would also be a help.  I checked off the "Info" box there but it still doesn't do anything.  Under "Show items of type:" I'd like to add a "LINT Issues" type but there seems to be no way to do that or help describing this area.

     

    Thanks,
    Barry

  • 0 in reply to Barry Robertson
    Expert 1120 points

    Barry,

    I still have heard NOTHING from TI regarding this issue.  Anyone from TI actually monitoring these threads?  Hello?  Is this thing on?

    Clearly they can use the problems tab for parsing their output messages.  How tough is it to describe the rules so that other pre- and post-build tools can try to use the same format?

    I am getting more discouraged with the CCSv4 tools every day.

    I will let you know if I hear of any way to do this.

    Scott

  • 0 in reply to Scott Whitney
    Prodigy 20 points

    I have contacted them multiple times as well with one reply that referred me to a blog that I don't have access to.  No reply when I pointed that out.

  • 0 in reply to Barry Robertson
    Genius 4130 points

    Hi Barry,

    I've just figured out that the keyword is 'remark' and not 'info'. This will then be output in the CCS 5.5 'Advice' tab rather than the 'Problems' tab.

    Regards, Tony.