no .log file created for a crash?

stephenfewer / grinder

Grinder is a system to automate the fuzzing of web browsers and the management of a large number of crashes.

BSD 3-Clause "New" or "Revised" License

414 stars 131 forks source link

no .log file created for a crash? #28

Closed van7hu closed 10 years ago

van7hu commented 10 years ago

Hi,

I have obtained about a handful of crashes from grinder when I fuzz Chrome on windows XP using the nduja fuzzer. However, for a crash, there's a file called "58DCB01E.0BC01241.crash" could be downloaded through grinder remote server, but the file "58DCB01E.0BC01241.log" has the size of 0 byte when listed on server, and when I click download that file, it resulted in "file not found".

What would be the problem here?

van7hu commented 10 years ago

Also, when I seach computer for "58DCB01E.0BC01241.log", there's no file with that name. There's just "58DCB01E.0BC01241.crash" in the crashes/ folder.

stephenfewer commented 10 years ago

Hi, this can happen for several reasons, I put a small wiki entry to go over some of them:

https://github.com/stephenfewer/grinder/wiki/Troubleshooting-Grinder-logging-failure

I should point out the nduja fuzzer may not be fully compatible with Grinder due to how it handles event callbacks, however it should still be creating log files. Hopefully the above wiki entry will help.

I'll double check the latest Chrome is still logging correctly as sometimes updates break the hooking stubs.

stephenfewer commented 10 years ago

Yup I can confirm the hooking stubs are working fine for latest Chrome (Version 33.0.1750.149 m). So the problem it probably one of the others listed in the wiki.