<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr">On Fri, 11 May 2018, 02:19 Cillian O'Donnell, <<a href="mailto:cpodonnell8@gmail.com">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"><br><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_quote">On 10 May 2018 at 20:15, Vijay Kumar Banerjee <span dir="ltr"><<a href="mailto:vijaykumar9597@gmail.com" target="_blank" rel="noreferrer">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">Frankly, I'm totally confused at the moment. I'm not able to come up with a proper task list to serially go through.<div><br></div><div>according to my understanding (and proposal), the major goals are: </div><div><br></div><div>1. Get the coverage analysis running again and get it merged with the current master repo.</div></div></blockquote><div><br></div><div>Yep, this is definitely the most immediate goal.<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>2. Generating line coverage reports using the gcov/lcov .</div><div>3. get covoar generate reports on a data-centric format (as Joel suggested in the proposal earlier, this needs a discussion on the choice of format. Chris probably has some thoughts about it.)</div><div><br></div><div>looking at the above and the current status I need to break down it into subtasks. Here are some of the questions that'll help me understand properly.</div><div><br></div><div>1. before the current updates to covoar, the coverage analysis was generating the html and txt reports (which I posted) in the previous set up. Is that what we're targeting to achive with the current setup?</div></div></blockquote><div><br></div><div>Exactly we need to see it doing what it was before and then this will be a good jumping off point for the other goals.<br></div></div></div></div></blockquote></div></div><div dir="auto">got it , It's Clear now.</div><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> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>2. The covoar is under update as Chris is working on it, there are still some issues there, updating the main() module is, I guess, one of them. This needs to be done as the first step before the tester can generate reports. </div></div></blockquote><div><br></div><div>What Chris is doing now, we can keep an eye on what's happening and help with testing but we won't need to wait for it to move forward. So getting the tester to run covoar is separate and we can crack on with that.<br></div></div></div></div></blockquote></div></div><div dir="auto">Understood.</div><div dir="auto">have you set any 'plan' for how to approach this ?</div><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></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div><div><div class="gmail_extra"><span><br clear="all"><div><div class="m_4167356449631049506m_-5675870814509029103m_-8090682357301293004gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr">On 10 May 2018 at 23:40, Joel Sherrill <span dir="ltr"><<a href="mailto:joel@rtems.org" target="_blank" rel="noreferrer">joel@rtems.org</a>></span> wrote:<br></div></div></div></div></span><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><div class="m_4167356449631049506m_-5675870814509029103m_-8090682357301293004h5"><span>On Thu, May 10, 2018 at 12:37 PM, Cillian O'Donnell <span dir="ltr"><<a href="mailto:cpodonnell8@gmail.com" target="_blank" rel="noreferrer">cpodonnell8@gmail.com</a>></span> wrote:<br></span><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div><div class="m_4167356449631049506m_-5675870814509029103m_-8090682357301293004m_2824552953364384595gmail-h5"><div><div class="gmail_quote"><div dir="ltr">Ahhh I see, more c++ conversion for the rest of covoar, or at least the parts called in main. That's something Vijay could do, the blueprint for the conversion is in one of Chris last patches updating covoar.cc Any objections to him doing it Joel, Chris?<br></div></div></div></div></div></div></blockquote><div><br></div></span></div></div><span><div>None from me. This particular issue would be higher than many of the</div><div>other things Chris wants changed since it manifests as a bad exit().</div></span></div></div></div></blockquote><div>I can surely try looking into it (any instructions ?). Also, Isn't Chris already on it ? </div><span><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><br></div><div>But overall Vijay needs to get output from covar with covoar running</div><div>cleanly (no faults) so he can focus on gcov output and reporting</div><div>improvements.</div><div><br></div><div>NOTE: I am still open to the idea that gcov, lcov, etc. may be able to</div><div>produce reports that we are completely happy with. They need to</div><div>at least be a working alternate. lcov output looks promising from </div><div>the samples I have seen:</div><div><br></div><div><a href="http://ltp.sourceforge.net/coverage/lcov/output/index.html" target="_blank" rel="noreferrer">http://ltp.sourceforge.net/coverage/lcov/output/index.html</a></div></div></div></div></blockquote><div><br></div></span><div>the report looks good </div><span><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> </div></div></div></div></blockquote><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><br></div><div><br></div><div><a href="https://swarminglogic.com/jotting/2014_05_lcov" target="_blank" rel="noreferrer">https://swarminglogic.com/jotting/2014_05_lcov</a> has more complicated reports</div><div>and instructions. It even includes a shell script to make Chris happy. LOL<br></div></div></div></div></blockquote></span><div>thanks for the link, the inscructions are really helpful to get started.</div><span><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>Vijay.. my thought is that you need to get gcov files output from covoar.</div><div>Then automating running gcov or lcov (lcov looks nicer I think). That should</div><div>be a nice place to be completely committed. Hopefully at this point, you</div><div>will be analyzing all of cpukit/ and we can find some discrepancies between</div><div>covoar reports and lcov/gcov output. Then fix those. That's just my thoughts</div><div>though.</div></div></div></div></blockquote></span><div>+So after the covoar runs with no issues and the coverage report shows some data, the next work is to generate gcov output .</div><div>+ Then automating running lcov .</div><span><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><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span><div dir="auto"><span class="m_4167356449631049506m_-5675870814509029103m_-8090682357301293004m_2824552953364384595gmail-"><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
I also need to figure out why the address has lost it's reference to the source<br>
table.<br>
<br>
Chris<br>
</blockquote></div></div></span></div>
<br></span><span>_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@rtems.org" target="_blank" rel="noreferrer">devel@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br></span></blockquote></div><br></div></div>
<br>_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@rtems.org" target="_blank" rel="noreferrer">devel@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br></blockquote></span></div><br></div></div></div>
</blockquote></div><br></div></div>
</blockquote></div></div></div>