Re: [COVERITY ACCESS] for Embedded/Automotive team

[Artem Mygaiev <artem_mygaiev@epam.com>]

Coverity Scan does static analysis only, but hooks into the build system
in order to track compilation process and build map of source code to
analyze.

In addition to connecting the build process, user of Scan needs to
provide a) filters to specify particular components for analysis and b)
model that implements "library" functions like synchronization, memory
allocation, etc.

[1] http://www.coverity.com/products/coverity-save/

On 22.11.16 13:55, Lars Kurth wrote:
> On 22/11/2016 11:51, "Julien Grall" <julien.grall@arm.com> wrote:
>
>> Hi Lars,
>>
>> On 19/11/16 16:53, Lars Kurth wrote:
>>> On 18/11/2016 20:55, "Julien Grall" <julien.grall@arm.com> wrote:
>>>> Coverity has been proven useful on x86 to catch some bugs. A such
>>>> things
>>>> would be nice for ARM too. Is there anything we can do to get coverity
>>>> testing ARM? (CC Lars).
>>> Coverity does static code analysis. It analyses our entire tree,
>>> although
>>> I don't know whether we updated it to point it to new repos such as the
>>> mini-os one.
>> I thought coverity was hooking into the build system by replacing the
>> compiler, right?
>>
>> If so, how does coverity analyze xen/arch/arm?
> I guess that is a question for someone else who is more familiar with the
> set-up. But there shouldn't be any technical reason which prevents
> Coverity scan from running on any CPU specific code.
>
> Lars
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel