Nice to see that I'm only 3 weeks behind the curve!
> On May 8, 2017, at 2:58 PM, Kurt Schwehr <schw...@gmail.com> wrote: > > Yup... https://lists.osgeo.org/pipermail/gdal-dev/2017-April/046495.html > > I'd be happy if anyone else wanted to take lead on it. > > I've created https://trac.osgeo.org/gdal/ticket/6883 > > Since I'm internal to google, I've been running some fuzzer targets against > gdal behind the scenes and used the results to fix a number of bugs. I've > added a number of fuzz targets to > https://github.com/schwehr/gdal-autotest2/tree/master/cpp and modified GDAL > to make fuzzing more productive... e.g. > > https://trac.osgeo.org/gdal/changeset/37592/ adds > FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION to a driver > https://trac.osgeo.org/gdal/changeset/37909 example fix > > I have ~50 bugs that I haven't gotten to. > >> On Mon, May 8, 2017 at 11:46 AM, Jesse McGraw <jlmcg...@gmail.com> wrote: >> I think the gdal suite would be a perfect candidate for this project from >> google. Is anyone interested in trying to integrate gdal into it? >> >> https://opensource.googleblog.com/2017/05/oss-fuzz-five-months-later-and.html?m=1 >> _______________________________________________ >> gdal-dev mailing list >> gdal-dev@lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/gdal-dev > > > > -- > -- > http://schwehr.org
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev