DavidKorczynski

I can now build NSS with fuzz-introspector: The issue is that NSS uses a lot of processes during compilation and each of these also uses a lot of memory. This...

> Division by zero in `post-processing/main.py` > These projects encounter div by zero once the profile is not produced or fail to merge: ~~Div by zero fixed in https://github.com/ossf/fuzz-introspector/commit/b03c4cfcfbec51779133adf24d14d78425e9121c~~

https://github.com/ossf/fuzz-introspector/issues/30#issuecomment-1028514294 Kamailio should be fixed with https://github.com/ossf/fuzz-introspector/commit/554ae742c4d576da2b6334e132cda1ad6e016316 have run locally where I verified the issue and also verified post-fix that it works now

> Division by zero in `post-processing/main.py` These projects encounter div by zero once the profile is not produced or fail to merge: > > * croaring > * nettle >...

I added a small script to automate testing projects of oss-fuzz projects here https://github.com/ossf/fuzz-introspector/blob/main/oss_fuzz_integration/test_projects.sh

> introspector's pass is the main cause of build failure: Do you mean here it's specifically to compiler pass or do some of these projects fail in the post-processing?

`quickjs` is working for me

`wuffs` is working for me, although the reports have fairly limited calltrees, and I think this is because of use of indirect pointers, e.g.: https://github.com/google/wuffs/blob/ccbec1833094b1d2ee18b969aaae356a46bc5b30/internal/cgen/base/pixconv-submodule.c#L5270-L5281 Ref https://github.com/ossf/fuzz-introspector/issues/4

Are we sure that all of these projects are related to fuzz-introspector? I am asking this because I debugged an issue over here https://github.com/ossf/fuzz-introspector/issues/48#issuecomment-1063163173 where it seems that the issue...

The space between callsite 185 and callsite 186 is reported as the blocker, i.e. not the function ext2fs_free_mem. The horisontal line between the two callsites is the blocker as such....