Hi Pascal, There is also this one: http://drmemory.org/
- Andrejs > On 15.06.2015, at 15:14, Pascal Cuoq <[email protected]> wrote: > > Hello, > > I am working on a C interpreter that uses existing tests to find more issues > than simple execution does. In that it is comparable to Valgrind or UBSan. It > has different enough strengths and weaknesses compared to these existing > tools to make it worth using in addition to them, too. > > This C interpreter is already able to work its way through a majority of the > tests in OpenSSL's test directory, and indeed to find issues that occur > during the execution of these tests (RT #3891). I was wondering whether > anyone had, as a readily available artefact of fuzzing or quality assurance > campaigns, some additional test drivers beyond but in the same style as those > inside the archive. > > Tests for derived libraries such as LibreSSL or BoringSSL would also be > interesting. > > Making the interpreter available in its current state to a motivated third > party is also a possibility. > > Pascal > > _______________________________________________ > openssl-dev mailing list > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev _______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
