[SBFT24] Pastis

[cnheitman]

No description provided.

[vrthra]

Dear participants,

Thank you for the PR. This is a heads-up that your branch will need to be rebased on the SBFT branch once it is ready. We are still in progress of preparing the branch and will message you once we are done. This branch adds the functionality of adding mutation testing as a measurement criteria. We do not expect this to affect the fuzzer integration. Hence, we do not expect any conflicts, however, if there are any, we will help you resolve them.

[phi-go]

Hey, from our runs it seems like Pastis (pastis-aflpp) might leak some memory and requires around 8 GB RAM after 24 hours. While it likely won't be a problem for the competition, we cannot guarantee it. Would it be possible to reduce the memory usage?

[cnheitman]

Hi! Thanks for letting me know. I will check pastis-aflpp as soon as I have some time and try to determine what's going on. On the other hand, we are aware that Pastis in general requires some memory, however, we don't have a solution for that at the moment.

[phi-go]

So we talked with @alan32liu and it looks like the available memory for fuzzer worker VM's is 3.75GB, so this could likely be an issue after all.

[vrthra]

Dear Christian,
We have not received your tool report yet. Could you please send it to us soon? Furthermore, we would need a list of all authors, including mail, affiliation, and country to register the report? Note that we need to share this information with ICSE urgently

[phi-go]

Dear participants,

as already mentioned by Rahul in the Google Groups for SBFT'24, the tool reports can only be two pages long, instead of the four as mentioned in our timeline (including the references). As being over this two page limit will likely result in a rejection of your report by ACM, we wanted to also provide this information here to make sure it reaches you.

With Best Regards,
Fuzzing Competition Team.