User: Password:
|
|
Subscribe / Log in / New account

Re: MIT discovered issue with gcc

From:  Paul Wise <pabs-AT-debian.org>
To:  "debian-security-AT-lists.debian.org" <debian-security-AT-lists.debian.org>
Subject:  Re: MIT discovered issue with gcc
Date:  Sun, 24 Nov 2013 08:00:50 +0800
Message-ID:  <CAKTje6HzR-p2nNHKU_24rP7VgSb02JET_fB9cY2bWurcGAA3og@mail.gmail.com>
Cc:  debian-user <debian-user-AT-lists.debian.org>
Archive-link:  Article

On Sun, Nov 24, 2013 at 3:53 AM, Darius Jahandarie wrote:

> Although Debian *developers* can't find and fix all upstream bugs, the
> Debian project, as the funnel between code and users, provides an
> interesting location to perform this sort of automated static analysis
> on all source code flowing through it, and present that information
> to both the package maintainers and users of the packages.

Some Debian folks are working on that in conjunction with Fedora. We
could use some help, especially with packaging new checkers and with
writing firehose output converters for existing checkers. Please get
involved, links below.

PS: STACK isn't currently possible to package because it needs a
special build of llvm that isn't in Debian yet.

https://fedoraproject.org/wiki/StaticAnalysis
https://github.com/fedora-static-analysis/firehose
http://debile.debian.net/
http://firewoes.debian.net/
http://debuild.me/
https://wiki.debian.org/HowToPackageForDebian#Check_point...

-- 
bye,
pabs

http://wiki.debian.org/PaulWise




(Log in to post comments)


Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds