Add a way to save hard crashes #10

Activity

1. yevgenypats commented on Dec 18, 2019

   

   yevgenypats

   on Dec 18, 2019

   More actions

   heap-corruption issues in the runtime itself? this is cool!(would love to see that when possible/fixed). The only way I can think of saving those kind of crashes are saving each time the last input on disk but that will kind of slow the whole thing down. Do you have some kind of reproduction for this? maybe it's just running out of memory?
2. jvoisin commented on Dec 18, 2019

   

   jvoisin

   on Dec 18, 2019

   ContributorAuthor

   More actions

   I thought about keeping everything, but it would murder the performances.
   A better way would be to have a better monitoring of the fuzzee's process, to detect this kind of issues, and dump the input.

   I'm currently trying to run my fuzzer in an ASAN environment, to see if I can reproduce this.
3. yevgenypats commented on Dec 18, 2019

   

   yevgenypats

   on Dec 18, 2019

   More actions

   If you have a reproduction you can share I'll be happy to take a look at this. sounds like an interesting case-study.
4. jvoisin commented on Dec 18, 2019

   

   jvoisin

   on Dec 18, 2019

   ContributorAuthor

   More actions

   You can always use something like this I guess:

   import ctypes
   
   i = ctypes.c_char(b'a')
   j = ctypes.pointer(i)
   c = 0
   while True:
       j[c] = b'a'
       c += 1
5. yevgenypats commented on Dec 19, 2019

   

   yevgenypats

   on Dec 19, 2019

   More actions

   Ah got it, you meant code that uses cbindings. That makes more sense now.