Code Coverage in Lisaac is here

[Mildred Ki'Lya]

On 03/08/2010 07:36 PM, Nicolas Boulay wrote:
> I read quickly the report from git. I deduce that you modify the
> compilier it self to add the feature.
>
> I just said that almost everything a coverage tool need, are in the
> boolean prototype or in the BLOCK prototype, to add traceability
> monitoring.
>   
I don't see how you can get coverage without modifying the compiler.
Modifying the library can give you coverage of blocks (but then, you
need introspection to know where the block was). But this doesn't give
you the lists, and this is a problem.

The other solution would be to have the compiler produce advanced
position information in the resulting executable (using DWARF
<http://dwarfstd.org/> for example) and have an external tool like qemu
running your program and generating coverage information.

Mildred

-- 
Mildred Ki'Lya
╭───────── ｍｉｌｄｒｅｄ５９３＠ｏｎｌｉｎｅ．ｆｒ ──────────
│ Jabber, GoogleTalk: <mildred at jabber.fr>
│ Website: <http://ki.lya.online.fr>           GPG ID: 9A7D 2E2B
│ Fingerprint: 197C A7E6 645B 4299 6D37 684B 6F9D A8D6 9A7D 2E2B
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/lisaac-devel/attachments/20100308/5e990e39/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/lisaac-devel/attachments/20100308/5e990e39/attachment.pgp>