Re: [lwip-devel] Reporting crashes found by running a fuzzing campaign

[Hiromasa Ito]

Hi, Simon.

Thanks for your refactoring and merging my suggestion!

I have no idea why the 003 does not trigger anything,
but I will post if I get something about that :)

Best regards,
Hiromasa

On 2020/02/21 6:00, address@hidden wrote:
> Hey!
>
> Am 05.12.2019 um 07:25 schrieb Hiromasa Ito:
> > Hi, Simon.
> >
> > I made patches for lwip and lwip-contrib (both are for v2.1.0.RC1).
> > The lwip patch generates my test driver and modifies Makefile and lwipopts.h a 
> > little.
> > The lwip-contrib patch modifies UNIX-ported sys_arch.c to make sys_now() fuzzy.
> >
> > To build my test driver, run this command at test/fuzz:
> > `make triple_fuzz D='-DFUZZED_TMR'`
> >
> > After that, to reproduce crashes, run this command:
> > `./triple_fuzz <crashed_input_file>`
> >
> > crashed_input.tar.gz contains nine crashed input files.
> > Each file reproduces crashes failed at different assertions.
> >
> > Please check them out!
>
> I've finally found the time to smoothly integrate these new tests into
> test/fuzz, now creating 3 binaries that execute tests in 3 different
> modes (where mode 3 is your work).
>
> Strangely, the file 003 does not trigger anything, but I'll work on the
> other 8 ;-)
>
> Regards,
> Simon