[Olsr-dev] static analysis of olsrd

[Aaron Kaplan]

First of all: this is wonderful!

But could you also explain the defects?
Because this will give a much better insight into further defects  
which will be out there and which were not discovered.

just my 2 cents...

besides we said in OLSR-NG that all patches should go thru bernd as a  
quality control instance.
And that really payed off so far :) (patting bernd on the shoulder ;-)

best,
aaron.


On Oct 5, 2007, at 12:26 AM, David Cornejo wrote:

> Hi,
>
> My employer is going to be using olsrd (on FreeBSD).  We develop
> medical equipment and so need to run all the code used through a QA
> suite which includes a static analysis tool (Coverity Prevent).  I
> would like to modify the code to fix some/all of the defects found and
> commit them to the tree.
>
> First, is there any objection to this?  If not, then would people
> prefer a patch posted for review or should I just commit it (I think I
> still have commit privs on sourceforge) and see what happens?
>
> Unfortunately I cannot provide others with access to the defects
> viewer, though I can try and put together a summary if there's
> interest.
>
> I pulled a snapshot from yesterday and came up with a total of 23
> defects (in 29129 lines of code) - which is about 0.790 defects per
> 1000 lines of code.  (for reference, a snapshot of the Linux kernel
> had 0.127, FreeBSD had 0.386).
>
> thanks,
> dave c
> Hoana Medical, Inc.
> Honolulu, HI USA
>
> -- 
> Olsr-dev mailing list
> (spam-protected)
> http://lists.olsr.org/mailman/listinfo/olsr-dev
>

---
there's no place like 127.0.0.1