Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51D0B835.2080901@gentoo.org>
Date: Mon, 01 Jul 2013 00:59:01 +0200
From: Luca Barbato <lu_zero@...too.org>
To: musl@...ts.openwall.com
Subject: Re: Request for volunteers

On 06/30/2013 05:25 PM, Nathan McSween wrote:
>> 5. Rigorous testing. My ideal vision of this role is having somebody
>>    who takes a look at each bug fix committed and writes test cases
>>    for the bug and extrapolates tests for possible related bugs that
>>    haven't yet been found. And who reads the glibc bug tracker so we
>>    can take advantage of their bug reports too.
> 
> This could be found using something like llvms Klee or any other smt bug
> finder. IMO conformance tests should be written with the project otherwise
> what is currently happening with musl (conformance tests don't exist or
> have bugs) happens.
> 
I suggest sparse[1], it is less known but decent.

[1]https://sparse.wiki.kernel.org/index.php/Main_Page

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.