<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 03/08/2010 07:36 PM, Nicolas Boulay wrote:
<blockquote
cite="mid:d22d8a041003081036t42a81b7cw1d0eb8537ab69b16@mail.gmail.com"
type="cite">
<pre wrap="">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.
</pre>
</blockquote>
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.<br>
<br>
The other solution would be to have the compiler produce advanced
position information in the resulting executable (using <a
href="http://dwarfstd.org/">DWARF</a> for example) and have an
external tool like qemu running your program and generating coverage
information.<br>
<br>
Mildred<br>
<br>
<pre class="moz-signature" cols="72">--
Mildred Ki'Lya
╭───────── ｍｉｌｄｒｅｄ５９３＠ｏｎｌｉｎｅ．ｆｒ ──────────
│ Jabber, GoogleTalk: <a class="moz-txt-link-rfc2396E" href="mailto:mildred@jabber.fr"><mildred@jabber.fr></a>
│ Website: <a class="moz-txt-link-rfc2396E" href="http://ki.lya.online.fr"><http://ki.lya.online.fr></a> GPG ID: 9A7D 2E2B
│ Fingerprint: 197C A7E6 645B 4299 6D37 684B 6F9D A8D6 9A7D 2E2B
</pre>
</body>
</html>