<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 21 May 2018 at 02:29, Cillian O'Donnell <span dir="ltr"><<a href="mailto:cpodonnell8@gmail.com" target="_blank">cpodonnell8@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><span><div><br><br><div class="gmail_quote"><div dir="ltr">On Sun, 20 May 2018, 15:35 Vijay Kumar Banerjee, <<a href="mailto:vijaykumar9597@gmail.com" target="_blank">vijaykumar9597@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 20 May 2018 at 00:53, Vijay Kumar Banerjee <span dir="ltr"><<a href="mailto:vijaykumar9597@gmail.com" rel="noreferrer" target="_blank">vijaykumar9597@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="auto"><div><br><br><div class="gmail_quote"><span><div dir="ltr">On Sun, 20 May 2018, 00:45 Cillian O'Donnell, <<a href="mailto:cpodonnell8@gmail.com" rel="noreferrer" target="_blank">cpodonnell8@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">It works.. Sorry I was using the right covoar but the wrong rtems-test. Ahh its nice to see the data back in the reports again. Did you manage to track down 2 exes with the mismatch in symbol size?<br></div></blockquote></span><div>Great! so next is the parsing of the symbol file.</div><div>I couldn't manage to track down the mismatch.<br></div></div></div><div dir="auto"><br></div></div></div></blockquote><div>I have pushed these to my master branch.</div><div><br></div><div>The latest update to cov-tester-support branch (please have a look)</div><div>parses the symbol-set ini file from the coverage script. The parsing </div><div>is working but currently it's not generating reports, as covoar</div><div>needs to be updated . </div></div></div></div></blockquote></div></div><div dir="auto"><br></div></span><div dir="auto">It's best if covoar reads it's own config file, otherwise it creates a dependency on the tester. Scanning over the recent changes to covoar there, it looks like it can already handle multiple sets, so the one ini with multiple sets in it is the way to go.</div></div></blockquote><div>Okay, Understood.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><span><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Here are the things that I have done and that needs to be</div><div>done in order to generate reports :</div><div><br></div><div>I have added a symbol-sets.ini file and parsed it from the coverage script <br>this is how it works :<br><div><br></div></div><div><ul><li>The ini file can be updated with all the symbols, separated by ' , ' (comma)<br></li></ul></div></div></div></div></blockquote></div></div><div dir="auto"><br></div></span><div dir="auto">This is the way covoar is actually handling it now. You should test a multi set ini and see if that's working.</div></div></blockquote><div>Yeah, I have seen it. will try with multiple sets.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><span><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><ul><li></li><li>The coverages splits them and makes a list of all the sets</li><li> The respective libraries are parsed from the libraries section.</li><li>It returns a dict with all the symbols and thir resp. library addresses.</li><li>The library addresses are absolute so it can be run from anywhere<br>top of build tree is not necessary.</li></ul></div></div></div></div></blockquote></div></div></span><div dir="auto">This was a good idea but it's just that dependency issue we want to stay away from. Covoar has something to find the build directory too, it just hasn't been connected up yet, so running it from the top of the build directory is ok for the moment.</div></div></blockquote><div> </div><div>yes it can find the build directory. I was giving it a shot to do it from the script. </div><div><br></div><div>If covoar's standalone working is a necessity then it surely needs to be working<br></div><div>from covoar and shouldn't depend on the script. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div dir="auto"><br></div><div dir="auto">Probably the most pressing thing now is investigating those mismatch in symbol size.</div></div></blockquote><div><br></div><div>any advice on where/how to look for it ? </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><span><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>This way we can parse all the symbols from the same ini file.</div><div><br></div><div>what needs to be done :</div><div><ul><li>I have added #FIXME s in the code , those are the small fixes that <br>would be needed .</li><li>The covoar needs to be updated. My proposal is that we can feed the<br>parsed dict to the covoar instead of feeding the symbol file and letting <br>covoar parse it ( As I mentioned previously). </li></ul></div></div><br></div></div>
</blockquote></div></div></span></div>
</blockquote></div><br></div></div>