I could download the report and look through it. I assume that's the standard output from the analyzer. For prioritization of looking at issues, it can be helpful if there is a way to group them by "area" which usually corresponds to the subdirectory. My scan showed one for a chain method in score/src. I think adding one line of code would fix that.
But I also saw one in calloc.c which I think would need to be marked as a false report. calloc() is supposed to return a pointer so it isn't a leak. Is there a way to tell the analyzer to ignore that specific issue in that method? Have you looked through the reports for things that look legitimate and easy to fix? I'm unsure of the scope of your GSoC project so not sure other than to say I looked through it quickly and was able to see the issues reported after I unzipped the report. Is the goal to get this integrated into the RTEMS.org buildbot? --joel On Mon, Apr 20, 2020 at 12:14 PM suyash singh <suyashsingh...@gmail.com> wrote: > Find the analysis here > https://drive.google.com/drive/folders/1FL_euXfAtlzezDf0Vwg5-WHM22z8lbFQ > > steps here > https://github.com/suyashsingh234/rtems-notes > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
