Hi! > >From what I have read, it should be possible to annotate code to make > >coverity > stop complaining. For example by adding following: > /* coverity[EVENT_TAG_NAME] */ > > I'm not exactly clear where to get "event tag names" yet, as these seem to be > different from error names that appear in *.err logs. > > Before I dig deeper into this, would anyone be opposed if we start adding > such annotation to LTP source?
I'm OK with adding a few annotations to places where LTP does something that needs to be done and what is normally a bug. As far as I remember we have a few places that dereference NULL to cause segfault that produce false-possitive warnings as well. Looking at the BAD_FREE the munmap03.c is nice example of that. However most of the BAD_FREE, if I understant it correctly, are result of unmaping only part of the mmaped memory. That is not really bug, but I guess that I can live with annotations for these as well if you want them. -- Cyril Hrubis chru...@suse.cz ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
