Coverity Scan Configuration?

[Joel Sherrill]

There are also some annotations that can silence warnings for suspect cases
of not having breaks in switches, etc. I recall a few places that adding
annotations would allow users to get cleaner runs.

--joel

On Thu, Jun 27, 2019, 5:31 PM Gedare Bloom <gedare at rtems.org> wrote:

> I have an interest and plan to work on this area soon. I made myself a
> note to look into the options, and whether any of the rules can be used out
> of the box for open source in https://devel.rtems.org/ticket/3710
>
> Gedare
>
> On Thu, Jun 27, 2019, 5:25 AM Joel Sherrill <joel at rtems.org> wrote:
>
>> It would be good to have some control over Scan options but I have never
>> seen anything on the Dashboard giving us any control like this. It appears
>> to be set to a specific set of options outside our control.
>>
>> Also if you follow the path down for help, they send you to Stack
>> Overflow.
>>
>> If we can figure out who to ask for help, it would be good. We also need
>> a model for our memory allocator and kernel locks. They do support that in
>> Scan
>>
>> --joel
>>
>> On Thu, Jun 27, 2019, 2:18 AM Sebastian Huber <
>> sebastian.huber at embedded-brains.de> wrote:
>>
>>> Hello,
>>>
>>> the RTEMS project uses Coverity Scan:
>>>
>>> https://scan.coverity.com/projects/rtems?tab=overview
>>>
>>> Can it be configured in the open source program variant? For example
>>> Coverity supports a couple of MISRA rules:
>>>
>>>
>>> https://www.synopsys.com/content/dam/synopsys/sig-assets/datasheets/coverity-misra-standards-ds-ul.pdf
>>>
>>>  From the reported defects for RTEMS I guess these rules are not enabled
>>> currently. Would it be possible to enable a subset of these rules in our
>>> current setup?
>>>
>>> --
>>> Sebastian Huber, embedded brains GmbH
>>>
>>> Address : Dornierstr. 4, D-82178 Puchheim, Germany
>>> Phone   : +49 89 189 47 41-16
>>> Fax     : +49 89 189 47 41-09
>>> E-Mail  : sebastian.huber at embedded-brains.de
>>> PGP     : Public key available on request.
>>>
>>> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>>> _______________________________________________
>>> devel mailing list
>>> devel at rtems.org
>>> http://lists.rtems.org/mailman/listinfo/devel
>>
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190627/8cdfd917/attachment.html>