News for hackers. Stuff that matters.
Re:How to Fuzz an ADT Implementation (2013) by agroce on Friday April 17, 2020 @07:15PM (#22903903)
https://blog.trailofbits.com/2019/01/22/fuzzing-an-api-with-... provides a little more friendly way (with delta-debugging and save/replay, and ability to use more fuzzers) to do this, via DeepState
Re:How to Fuzz an ADT Implementation (2013) by taborj on Friday April 17, 2020 @08:12PM (#22904207)
Yet another article that uses an acronym and then doesn't bother cluing us in to what it stands for.

I build healthcare interfaces; ADT means demographics. What's it mean here?

Re:How to Fuzz an ADT Implementation (2013) by zem on Friday April 17, 2020 @08:36PM (#22904328)
even in a programming context i thought it was going to be 'algebraic datatype'
Re:How to Fuzz an ADT Implementation (2013) by cryptonector on Friday April 17, 2020 @08:30PM (#22904296)
Abstract data type.
Re:How to Fuzz an ADT Implementation (2013) by antirez on Saturday April 18, 2020 @06:59AM (#22906848)
This is how rax (https://github.com/antirez/rax) and most of Redis is tested. Indeed this is the only way to be confident about a complex data structure implementation sanity.
Re:How to Fuzz an ADT Implementation (2013) by jkaptur on Friday April 17, 2020 @08:40PM (#22904342)
> Testing is necessarily incomplete but if you beat the crap out of the subset of the API that you actually intend to use, it’s possible to become reasonably confident that it will work in practice.

This is the kicker for me. I'm not a C++ expert, but knowing that a coverage-guided fuzzer has been running against my code for the past few months gives me a lot of confidence.