Closed jplopezy closed 4 years ago
Everything between lithium
and your command are the test used to determine if a reduction is still interesting. So that example will check that app.exe testcase.html
outputs the given assertion string to stderr/stdout.
If you're reducing a crash, try to replace outputs
with crashes
and remove that assertion string.
(nit: you have 2x --timeout parameters in your command)
You might want to also check that minidumps are being activated via this registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps
Name: DumpType Type: REG_DWORD
See this MSDN page. That way, a dump should be generated instead of having windbg run.
If you need further help with this, please ask in https://riot.im/app/#/room/#fuzzing:mozilla.org
Hi,
i'm trying use lithium on windows to reduce a testcase html crash of some app.
C:\Python27>python.exe -m lithium outputs --timeout=5 --timeout=120 "ASSERTION: index out of range" C:\app.exe testcase.html Intermediate files will be stored in tmp3. The original testcase has 822 lines. Checking that the original testcase is 'interesting'...
The first error, which maybe I make is that I put "ASSERTION: index out of range", I do not understand that argument or that I should put according to the app or the file to be tested.
Currently the result is that the windbg is open with the crash and nothing else happens, except that it closes it by hand (the windbg) there ends the program.
Intermediate files will be stored in tmp3. The original testcase has 822 lines. Checking that the original testcase is 'interesting'... Exit status: TIMED OUT (409.658 seconds) Lithium result: the original testcase is not 'interesting'! Tests performed: 1 Test total: 822 lines