coverage reports and "unknown"
Joel Sherrill
joel.sherrill at OARcorp.com
Sat Aug 25 21:47:16 UTC 2012
cc'ing Sebastian since _Protected_heap_Iterate showed up.
Hi
I did a coverage run locally and got a couple of entries
with "unknown". These turned out to be because there
were symbols in the libraries which never showed up
in an executable.
$ cat erc32-Ospd-20120825-1556/sizes_unreferenced.txt
100 _Timespec_Add_to unknown
44 _Protected_heap_Iterate unknown
If you grep for those symbols in the objdump or nm output
from all test executable, you won't see it. It simply is in
the librtemscpu.a and not referenced.
The rtems_syms.txt file is a full list of the public symbols
in the tested libraries. It is possible that a method is never
pulled into an executable. In that case, covoar has very little
information on it. It is just "unknown".
It really should be interpreted as "completely
unreferened and untested"
Krzysztof Hopefully you changed that with your new test. :)
--joel
More information about the devel
mailing list