  Crash report accumulation is a necessary step during continuous fuzzing.
Dynamic software analysis techniques like fuzzing and dynamic symbolic
execution generate a large number of crashes for analysis. However, the time
and resource constraints often lead to the postponement of fixing some less
critical issues, potentially introducing new errors in future releases. Thus,
there is a need to distinguish new errors from old ones. We propose a crash
accumulation method and implemented it as part of the CASR toolset. We
evaluated our approach on crash reports collected from fuzzing results.
