Re: Gcov support in Covoar

Hello, I have made the changes and also got the confusion with structure of gcno, cleared to some extent after some careful reading and experiments. I'm attaching the txt file generated. So far it is complete up to function record, next is the basic block records. I will start with the block

Re: Gcov support in Covoar

On 18 July 2018 at 02:30, Joel Sherrill wrote: > This definitely looks like the right direction. If we don't understand > the file formats, we will never be able to process and correlate them. > > Please put 0x in front of hex numbers. It does help. > > Can you explain the fields in

Re: Gcov support in Covoar

This definitely looks like the right direction. If we don't understand the file formats, we will never be able to process and correlate them. Please put 0x in front of hex numbers. It does help. Can you explain the fields in gcno_dump.txt? The Version field looks like hex for R37A which doesn't

Re: Gcov support in Covoar

I have filed a ticket for gcov, as suggested by Joel. https://devel.rtems.org/ticket/3468 -- vijay On 8 July 2018 at 01:43, Chris Johns wrote: > On 8/7/18 7:51 am, Vijay Kumar Banerjee wrote: > > On 8 July 2018 at 01:08, Joel Sherrill j...@rtems.org>> > > wrote: > > > > On Sat, Jul 7,

Re: Gcov support in Covoar

On 8 July 2018 at 01:08, Joel Sherrill wrote: > > > On Sat, Jul 7, 2018, 2:33 PM Chris Johns > wrote: > >> On 5 Jul 2018, at 3:07 am, Joel Sherrill > > wrote: >> > On Wed, Jul 4, 2018, 3:06 AM Chris Johns > > > wrote: >> > >> > How does this

Re: Gcov support in Covoar

On Sat, Jul 7, 2018, 2:33 PM Chris Johns wrote: > On 5 Jul 2018, at 3:07 am, Joel Sherrill > wrote: > > On Wed, Jul 4, 2018, 3:06 AM Chris Johns > > wrote: > > > > How does this fit into the RTEMS Tester tool? > > > > > > If you want to run

Re: Gcov support in Covoar

t;> vijaykumar9...@gmail.com> wrote: >>> >>>> On 4 July 2018 at 22:37, Joel Sherrill wrote: >>>> >>>>> >>>>> >>>>> On Wed, Jul 4, 2018, 3:06 AM Chris Johns wrote: >>>>> >>>>>> >>

Re: Gcov support in Covoar

>>> >>>> >>>> On Wed, Jul 4, 2018, 3:06 AM Chris Johns wrote: >>>> >>>>> >>>>> >>>>> On 4/7/18 5:55 pm, Vijay Kumar Banerjee wrote: >>>>> > On 4 July 2018 at 13:09, Ch

Re: Gcov support in Covoar

t;>> > On 4 July 2018 at 13:09, Chris Johns >> > <mailto:chr...@rtems.org>> wrote: >>> > >>> > On 4/7/18 5:38 pm, Chris Johns wrote: >>> > > On 4/7/18 4:52 pm, Vijay Kumar Banerjee wrote: >>> > >> >>>

Re: Gcov support in Covoar

t; On 4/7/18 4:52 pm, Vijay Kumar Banerjee wrote: > > >> > > >> I'm starting this thread for discussions on the gcov support > > >> in covoar. > > >> > > >> Current status is that the code in it (like in GcovData.cc) > r

Re: Gcov support in Covoar

t; On 4/7/18 4:52 pm, Vijay Kumar Banerjee wrote: > > >> > > >> I'm starting this thread for discussions on the gcov support > > >> in covoar. > > >> > > >> Current status is that the code in it (like in GcovData.cc) > r

Re: Gcov support in Covoar

ng this thread for discussions on the gcov support  > >> in covoar. > >> > >> Current status is that the code in it (like in GcovData.cc) remained > untouched  > >> for a long time and it had not been updated after the source tree  > reorga

Re: Gcov support in Covoar

On 4 July 2018 at 13:09, Chris Johns wrote: > On 4/7/18 5:38 pm, Chris Johns wrote: > > On 4/7/18 4:52 pm, Vijay Kumar Banerjee wrote: > >> > >> I'm starting this thread for discussions on the gcov support > >> in covoar. > >> > >> Curr

Re: Gcov support in Covoar

On 4/7/18 5:38 pm, Chris Johns wrote: > On 4/7/18 4:52 pm, Vijay Kumar Banerjee wrote: >> >> I'm starting this thread for discussions on the gcov support  >> in covoar. >> >> Current status is that the code in it (like in GcovData.cc) remained >> untouched 

Re: Gcov support in Covoar

On 4/7/18 4:52 pm, Vijay Kumar Banerjee wrote: > > I'm starting this thread for discussions on the gcov support  > in covoar. > > Current status is that the code in it (like in GcovData.cc) remained > untouched  > for a long time and it had not been updated

Gcov support in Covoar

Hello, I'm starting this thread for discussions on the gcov support in covoar. Current status is that the code in it (like in GcovData.cc) remained untouched for a long time and it had not been updated after the source tree reorganization which is why it runs into segmentation fault while trying

Re: gcov support in Covoar

needed to be done for it to get merged with the main repo. As it >>>> depends on the ongoing work on the covoar.cc and coverage.py, meanwhile I >>>> want to get started with the gcov support in covoar as I already have some >>>> coverage data in txt format

Re: gcov support in Covoar

om> wrote: >> >>> Hello, >>> >>> The coverage report is showing some data now (txt only). There is still >>> some work needed to be done for it to get merged with the main repo. As it >>> depends on the ongoing work on the covoar.cc and cove

Re: gcov support in Covoar

>> some work needed to be done for it to get merged with the main repo. As it >> depends on the ongoing work on the covoar.cc and coverage.py, meanwhile I >> want to get started with the gcov support in covoar as I already have some >> coverage data in txt format to compare

Re: gcov support in Covoar

s on the ongoing work on the covoar.cc and coverage.py, meanwhile I > want to get started with the gcov support in covoar as I already have some > coverage data in txt format to compare with . > > I would like to know the following points to get started: > > 1. What is the current state o

gcov support in Covoar

Hello, The coverage report is showing some data now (txt only). There is still some work needed to be done for it to get merged with the main repo. As it depends on the ongoing work on the covoar.cc and coverage.py, meanwhile I want to get started with the gcov support in covoar as I already have