From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jeffrey Karrels <karrelsj@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Static analysis: Code weaknesses
Date: Tue, 13 Mar 2012 12:47:08 -0400 [thread overview]
Message-ID: <20120313164708.GE19228@phenom.dumpdata.com> (raw)
In-Reply-To: <CAFw--Df+3UxXWqq63eo0f-98EeaisipX+eRr91qXouDkSfphSg@mail.gmail.com>
On Fri, Mar 09, 2012 at 10:10:52AM -0800, Jeffrey Karrels wrote:
> Hello All,
>
> I am in the starting stages of research into static code analysis of
> Xen (as well as correction/remediation). I noticed a lot of comments
> towards code {sonar, surfer}, coverity, splint, etc in the forums, but
> most of the activity was back from the 2006-2008 era. Is anyone active
> in this area right now? I don't want to duplicate work and even better
> it would be nice to get a group together with a specific common
> objective. From a licensing perspective I am not sure how it works yet
> as I know some of the commercial tools have very strict contracts on
> releasing analysis output. With that said though perhaps others are
> using commercial tools already and we could be steered to utilize
> similar tools in order to collaborate.
Have you looked at smatch and sparse?
>
> Thoughts?
>
> Jeff
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-03-13 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 18:10 Static analysis: Code weaknesses Jeffrey Karrels
2012-03-13 16:47 ` Konrad Rzeszutek Wilk [this message]
2012-03-13 17:03 ` Dario Faggioli
2012-03-14 18:01 ` Jeffrey Karrels
2012-03-14 18:58 ` Konrad Rzeszutek Wilk
2012-03-14 19:14 ` Jeffrey Karrels
2012-03-16 15:44 ` Jeffrey Karrels
2012-03-16 15:51 ` Konrad Rzeszutek Wilk
2012-03-16 16:10 ` Jeffrey Karrels
2012-09-05 20:13 ` Jeffrey Karrels
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120313164708.GE19228@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=karrelsj@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.