Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Coordinated testing (max 2 hours) 
Some questions regarding Codan:

a) Assignment to itself:

#define UNUSED(x) x = x
void foo(int x, int y)
{
    y = y; // y not used in function
    if ((x = getchar()) != x)
    {
       // Never executed
    }

}

This will trigger the Codan Warning, but:

#define UNUSED(x) x = x
void foo(int x, int y)
{
    UNUSED(y); // Codan does not trigger a warning here
    ...
}

This will not trigger the Codan Warning. Is that behaviour wanted?
I know from our MISRAC checks, that we use the first one to calm down compiler warnings, but then have to comment x = x; usually for some tools like pclint or QAC. Since comments are not usually added by the preprocessor, commenting a UNUSED(x) (defined in a header) does not work in QAC and pclint. 

b) First example above again.
I guess the if-condition here is not handled by the "Statement has no effect" Analysis? I have not found a "Condition is always true", some compiler output on these kind.
c) What are actually all the Codan tests checking? Several of the Checks share the same tooltip text 
---
Name resolution problem found by the indexer.

Sample Message:
Invalid argument 'X'
---
d) The Qt Syntax problem does not seem to search for anything. Or is this only filled with meaningful comments, if I create a Qt Project?
e) I guess, the documentation should be updated, e.g. I can not find any information about Codan in the Help. 



Am 29.05.2014 16:28, schrieb Marc Khouzam:

Hi,

as discussed in the Multicore Debug call, let's do some coordinated testing for the release.

I expect that no more than 2 hours from each of a small amount of volunteers will be sufficient.
If you can spend the time, let us know on the mailing list to start the ball rolling.

We've been using google docs for our internal testing effort and find it very good.
I've created a document that is public to all and does not require logging in to google.
The document can be accessed by many at the same time, so just open it and update it.

CDT wiki->Manual testing->8.4 testing
or
https://docs.google.com/spreadsheet/ccc?key=0AgqbIOVmRSR4dGFEY3UtYm1fMzRDdEMtV1NpV3JOMkE&usp=sharing

It contains tests for Debug which are not exhaustive, but are a start.  There is a section
for Codan but no real tests yet.  I'd like to see tests added for other CDT parts, for installation and
new ones for Debug as time goes on.  Please feel free to grow that document for this release, which
we will then copy for the next release.

RC2 is out and should be used for this testing.
Or you can take RC3 which will be out tomorrow.

If you find issues you should open bugs.  If you are not sure, you can email the list and ask about your findings.

An on-going effort will be to replace some of those manual tests with automated ones.  But until that is done,
it is good to at least have the manual ones.

Thanks in advance.

Marc

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

Back to the top