public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin@cygwin.com
Subject: Coverity Scan
Date: Fri, 25 Apr 2014 05:33:00 -0000	[thread overview]
Message-ID: <5359F391.8060309@tiscali.co.uk> (raw)

Coverity Scan [1] is a commercial (paid for) static analysis tool, but
they offer it to Open Source programmes for free. I was having a browse
through the list of Open Source programmes using Coverity Scan, and
noticed that Cygwin wasn't listed. Would there be any interest in
analysing the cygwin1.dll source code on a fairly regular basis? If so,
I would be happy to have a go at setting up an analysis job for Cygwin.

I would imagine this would be of interest to CGF, Corinna and anyone
else who regularly updates the Cygwin source code. Obviously, this is
only worth doing if the analysis results are looked at and acted upon.

There are some conditions associated with using Coverity Scan [2]. The
one thing that jumps out is that our relationship with RedHat might be
a stumbling block. We can but ask - the worst that can happen is that
they politely decline.

There have been a few hints on this list about a possible move from CVS
to git. If such a move were on the cards then that should probably
happen first - I wouldn't want the nugatory effort of getting this
working from CVS only to have to change it almost immediately.

Any thoughts?

Dave.

[1] - https://scan.coverity.com/
[2] - https://scan.coverity.com/faq#how-get-project-included-in-scan


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2014-04-25  5:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25  5:33 David Stacey [this message]
2014-04-25  8:35 ` Corinna Vinschen
2014-04-25 12:20   ` David Stacey
2014-04-25 13:33     ` Corinna Vinschen
2014-04-25 15:53   ` Christopher Faylor
2014-04-25 19:09     ` David Arnstein
2014-05-16 20:03     ` David Stacey
2014-05-16 20:35       ` Jeffrey Altman
2014-05-17 16:13         ` Corinna Vinschen
2014-05-17 10:13       ` Corinna Vinschen
2014-05-17 23:13         ` David Stacey
2014-05-19  8:36           ` Corinna Vinschen
     [not found] <CAO1jNwuZhQoyccTTGJWcdUJHHQjHeYc5GZEyG-Hci5kfLaMcTA@mail.gmail.com>
2014-04-25  9:10 ` Fwd: " Jan Nijtmans
2014-04-25 12:17   ` Corinna Vinschen
2014-04-25 15:55     ` Christopher Faylor

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=5359F391.8060309@tiscali.co.uk \
    --to=drstacey@tiscali.co.uk \
    --cc=cygwin@cygwin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).