[PATCH] Coverage : Use '.o' files for coverage analysis

Use the Object files in cpukit/ instead of the static library for Coverage analysis --- tester/rt/coverage.py | 27 -- tester/rtems/testing/coverage/symbol-sets.ini | 90 +-- 2 files changed, 66 insertions(+), 51 deletions(-) diff --git

Re: [PATCH] Coverage : Use '.o' files for coverage analysis

On Tue, Oct 16, 2018, 8:15 AM Chris Johns wrote: > Hi Vijay > > Thank you for the patch. > > On 13/10/2018 13:29, Vijay Kumar Banerjee wrote: > > Use the Object files in cpukit/ instead of the static library > > for Coverage analysis > > Are there any code change

[PATCH] Coverage : Use '.o' files for coverage analysis

Use the Object files in cpukit/ instead of the static library for Coverage analysis --- tester/rt/coverage.py | 27 -- tester/rtems/testing/coverage/symbol-sets.ini | 90 +-- 2 files changed, 66 insertions(+), 51 deletions(-) diff --git

Re: [PATCH 11/25] Merge sapi/Makefile.am into cpukit/Makefile.am

On Mon, 1 Oct 2018 at 11:22, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 25/09/2018 07:58, Chris Johns wrote: > > On 25/09/2018 15:30, Sebastian Huber wrote: > >> On 25/09/2018 00:27, Chris Johns wrote: > >> We would have to go from the symbol to the ELF file to the

Re: covoar SIGKILL Investigation

I have filed a ticket with all the information. https://devel.rtems.org/ticket/3515 On Sat, 1 Sep 2018 at 00:35, Joel Sherrill wrote: > > > On Fri, Aug 31, 2018 at 1:42 PM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> >> >> >> On S

Re: covoar SIGKILL Investigation

On Sat, 1 Sep 2018 at 00:01, Joel Sherrill wrote: > > > On Fri, Aug 31, 2018, 12:44 PM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> Hello, >> I have listed all the specific exes for which covoar fails. >> I have observed that covoar fa

Re: covoar SIGKILL Investigation

at 21:11, Vijay Kumar Banerjee wrote: > I will send the attachment offlist as it's too big for the list. > On Wed, 22 Aug 2018 at 21:07, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> The coverage for whole testsuite completed successfully, >> I h

Re: covoar SIGKILL Investigation

I will send the attachment offlist as it's too big for the list. On Wed, 22 Aug 2018 at 21:07, Vijay Kumar Banerjee wrote: > The coverage for whole testsuite completed successfully, > I have attached the zip file here and also included the js and css files > in it. > > coverage

Re: covoar SIGKILL Investigation

On Wed, 22 Aug 2018 at 01:55, Joel Sherrill wrote: > > > On Tue, Aug 21, 2018, 1:59 PM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> >> >> On Tue, Aug 21, 2018, 7:34 PM Joel Sherrill wrote: >> >>> >>> >>>

Re: covoar SIGKILL Investigation

On Tue, Aug 21, 2018, 7:34 PM Joel Sherrill wrote: > > > On Tue, Aug 21, 2018 at 2:14 AM, Chris Johns wrote: > >> On 21/08/2018 16:55, Vijay Kumar Banerjee wrote: >> > I tried running coverage with this latest >> > master, covoar is taking up all the memory

Re: covoar SIGKILL Investigation

I tried running coverage with this latest master, covoar is taking up all the memory (7 GB) including the swap (7.6 GB) and after a while, still gets killed. :( can there be something wrong with my environment? I tried running it on a different system, coverage did run for the whole testsuite for

Re: [PATCH v2] Coverage: Add support to generate separate reports for each symbol-set

ping :) On 3 August 2018 at 03:15, Vijay Kumar Banerjee wrote: > Hello, > > If you find some time, please do a final review of this patch and provide > suggestions if it's not mergeable yet :) > > There are only three days left, I seek some advice on the wrapup work on >

Re: [PATCH v2] Coverage: Add support to generate separate reports for each symbol-set

/gcno_dumper/blob/master/gcno_dump.txt <https://github.com/thelunatic/gcno_dumper/blob/master/gcno_dump.txt> * Any other suggestions ? Thanks --vijayk On 30 July 2018 at 22:55, Vijay Kumar Banerjee wrote: > Invoke covoar multiple times from the script to generate separate > repo

[PATCH v2] coverage/symbol-sets.ini : Add symbol-sets and paths to respective libraries

--- tester/rtems/testing/coverage/symbol-sets.ini | 48 +-- 1 file changed, 45 insertions(+), 3 deletions(-) diff --git a/tester/rtems/testing/coverage/symbol-sets.ini b/tester/rtems/testing/coverage/symbol-sets.ini index a2ec7bc..aac0b9b 100644 ---

[PATCH v2] Coverage: Add support to generate separate reports for each symbol-set

Invoke covoar multiple times from the script to generate separate reports for each symbol-set. --- tester/rt/coverage.py | 38 ++ 1 file changed, 18 insertions(+), 20 deletions(-) diff --git a/tester/rt/coverage.py b/tester/rt/coverage.py index

[PATCH v4] Coverage: Add support to generate separate reports for each symbol-set

Invoke covoar multiple times from the script to generate separate reports for each symbol-set. --- tester/rt/coverage.py | 38 ++ 1 file changed, 18 insertions(+), 20 deletions(-) diff --git a/tester/rt/coverage.py b/tester/rt/coverage.py index

Re: [PATCH] Coverage: Add support to generate separate reports for each symbol-set

On 30 July 2018 at 21:54, Gedare Bloom wrote: > On Mon, Jul 30, 2018 at 3:30 AM, Vijay Kumar Banerjee > wrote: > > Invoke covoar multiple times from the script to generate separate > > reports for each symbol-set. > > --- > > tester/rt/coverage.py | 32 +

[PATCH] Coverage: Add support to generate separate reports for each symbol-set

Invoke covoar multiple times from the script to generate separate reports for each symbol-set. --- tester/rt/coverage.py | 32 +++- 1 file changed, 15 insertions(+), 17 deletions(-) diff --git a/tester/rt/coverage.py b/tester/rt/coverage.py index 7dd5002..99342e1

Re: [PATCH v2 1/2] Coverage: Add support to generate separate reports for each symbol-set

On 30 July 2018 at 06:27, Chris Johns wrote: > On 26/07/2018 01:40, Vijay Kumar Banerjee wrote: > > Invoke covoar multiple times from the script to generate separate > > reports for each symbol-set. > > --- > > tester/rt/coverage.py | 42 ---

Re: [PATCH v2 1/2] Coverage: Add support to generate separate reports for each symbol-set

ping. :) On 25 July 2018 at 21:10, Vijay Kumar Banerjee wrote: > Invoke covoar multiple times from the script to generate separate > reports for each symbol-set. > --- > tester/rt/coverage.py | 42 -- > 1 file changed, 20 insertions(+

Re: [PATCH v2 2/2] coverage/symbol-sets.ini : Add symbol-sets and paths to respective libraries

On Thu, Jul 26, 2018, 11:29 PM Cillian O'Donnell wrote: > > > On Thu, 26 Jul 2018, 18:51 Vijay Kumar Banerjee, > wrote: > >> >> >> On Thu, Jul 26, 2018, 10:34 PM Cillian O'Donnell >> wrote: >> >>> Kryzstof is the original author, so h

Re: [PATCH v2 2/2] coverage/symbol-sets.ini : Add symbol-sets and paths to respective libraries

or the reply and for all the help throughout the summer. It was a great experience !! > >> On Thu, 26 Jul 2018, 17:22 Vijay Kumar Banerjee, < > vijaykumar9...@gmail.com> wrote: > >> Hello, >> >> I have a question which I forgot to ask before. >> Shoul

Re: [PATCH v2 2/2] coverage/symbol-sets.ini : Add symbol-sets and paths to respective libraries

Hello, I have a question which I forgot to ask before. Should the coverage.py and symbol-sets.ini files have mine and/or Cillian's name included in the copyright notice? --vijayk On 26 July 2018 at 13:09, Vijay Kumar Banerjee wrote: > I have added all the libs in cpukit and commented them

Re: [PATCH v2 2/2] coverage/symbol-sets.ini : Add symbol-sets and paths to respective libraries

I have added all the libs in cpukit and commented them out. Please have a look at the attached file. On 26 July 2018 at 04:50, Joel Sherrill wrote: > > > On Wed, Jul 25, 2018 at 10:41 AM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> --- >> tes

[PATCH v2 2/2] coverage/symbol-sets.ini : Add symbol-sets and paths to respective libraries

--- tester/rtems/testing/coverage/symbol-sets.ini | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/tester/rtems/testing/coverage/symbol-sets.ini b/tester/rtems/testing/coverage/symbol-sets.ini index a2ec7bc..3900f14 100644 ---

[PATCH v2 1/2] Coverage: Add support to generate separate reports for each symbol-set

Invoke covoar multiple times from the script to generate separate reports for each symbol-set. --- tester/rt/coverage.py | 42 -- 1 file changed, 20 insertions(+), 22 deletions(-) diff --git a/tester/rt/coverage.py b/tester/rt/coverage.py index

Re: [PATCH] Coverage: Add support to generate separate reports for each symbol-set

On 25 July 2018 at 20:06, Gedare Bloom wrote: > On Tue, Jul 24, 2018 at 10:37 PM, Vijay Kumar Banerjee > wrote: > > Invoke covoar multiple times from the script to generate separate > > reports for each symbol-set. > > --- > > tester/rt/coverage.p

[PATCH] Coverage: Add support to generate separate reports for each symbol-set

Invoke covoar multiple times from the script to generate separate reports for each symbol-set. --- tester/rt/coverage.py | 32 +-- tester/rtems/testing/coverage/symbol-sets.ini | 11 ++--- 2 files changed, 23 insertions(+), 20 deletions(-) diff

Re: coverage : error when running --coverage with rtems-test for whole testsuites

On 21 July 2018 at 03:49, Vijay Kumar Banerjee wrote: > On Fri, Jul 20, 2018, 10:08 PM Joel Sherrill wrote: > >> >> >> On Fri, Jul 20, 2018 at 9:14 AM, Gedare Bloom wrote: >> >>> On Thu, Jul 19, 2018 at 6:29 PM, Vijay Kumar Banerjee >>> wrot

Re: coverage : error when running --coverage with rtems-test for whole testsuites

On Fri, Jul 20, 2018, 10:08 PM Joel Sherrill wrote: > > > On Fri, Jul 20, 2018 at 9:14 AM, Gedare Bloom wrote: > >> On Thu, Jul 19, 2018 at 6:29 PM, Vijay Kumar Banerjee >> wrote: >> > Hello, >> > >> > I used the following command >>

Re: coverage : error when running --coverage with rtems-test for whole testsuites

On Fri, Jul 20, 2018, 9:19 PM Gedare Bloom wrote: > On Fri, Jul 20, 2018 at 11:43 AM, Vijay Kumar Banerjee > wrote: > > On 20 July 2018 at 19:44, Gedare Bloom wrote: > >> > >> On Thu, Jul 19, 2018 at 6:29 PM, Vijay Kumar Banerjee > >> wrote: > >

Re: coverage : error when running --coverage with rtems-test for whole testsuites

On 20 July 2018 at 19:44, Gedare Bloom wrote: > On Thu, Jul 19, 2018 at 6:29 PM, Vijay Kumar Banerjee > wrote: > > Hello, > > > > I used the following command > > > > > > $HOME/development/rtems/test/rtems-tools/tester/rtems-test \

coverage : error when running --coverage with rtems-test for whole testsuites

Hello, I used the following command $HOME/development/rtems/test/rtems-tools/tester/rtems-test \ --rtems-tools=$HOME/development/rtems/5 --log=coverage_analysis.log \ --no-clean --coverage=score --rtems-bsp=leon3-qemu-cov \

Re: Gcov support in Covoar

records after finalizing the wrapup of the non-gcov coverage reports to make sure that everything works properly there. -- vijay On 18 July 2018 at 17:17, Vijay Kumar Banerjee wrote: > On 18 July 2018 at 02:30, Joel Sherrill wrote: > >> This definitely looks like the right direction.

Re: Gcov support in Covoar

ing on figuring out how the file is organised, I'll post the generated txt file soon. > But this is what it takes to understand it. :) > > --joel > > > On Sat, Jul 14, 2018 at 4:29 PM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> Hello, >> >

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: >

Re: [PATCH v3] coverage : Add support to run coverage in supported bsp without extra options

On 11 July 2018 at 02:49, Chris Johns wrote: > On 11/7/18 3:18 am, Vijay Kumar Banerjee wrote: > > On 10 July 2018 at 20:47, Gedare Bloom > <mailto:ged...@rtems.org>> wrote: > > > > I don't see any problem with it, but I prefer to let Chris decide

Re: [PATCH v3] coverage : Add support to run coverage in supported bsp without extra options

ping :) On 6 July 2018 at 02:08, Vijay Kumar Banerjee wrote: > Hello Chris, > > If you find some time, please review this patch. > It's a small patch but it's important since it affects how the command > will look like. > > please review if this patch is alright or we nee

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 6 July 2018 at 23:50, Joel Sherrill wrote: > > > On Thu, Jul 5, 2018, 3:31 PM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> I think that the whole gcov support needs to be reworked. >> > > I am unsure the scope of what you have in m

Re: [PATCH v3] coverage : Add support to run coverage in supported bsp without extra options

Hello Chris, If you find some time, please review this patch. It's a small patch but it's important since it affects how the command will look like. please review if this patch is alright or we need to have a different approach. Thanks On 3 July 2018 at 20:30, Vijay Kumar Banerjee wrote

[PATCH] tester/covoar/coverage_converter.cc: Fix typo

--- tester/covoar/coverage_converter.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tester/covoar/coverage_converter.cc b/tester/covoar/coverage_converter.cc index 8144d93..fffa2d6 100644 --- a/tester/covoar/coverage_converter.cc +++ b/tester/covoar/coverage_converter.cc

Re: Gcov support in Covoar

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

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

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

[PATCH v3] coverage : Add support to run coverage in supported bsp without extra options

Close #3440 --- tester/rt/test.py| 21 ++--- tester/rtems/testing/bsps/leon3-qemu-cov.ini | 1 + 2 files changed, 15 insertions(+), 7 deletions(-) diff --git a/tester/rt/test.py b/tester/rt/test.py index 9214ad6..5d25d82 100644 --- a/tester/rt/test.py

Re: Query regarding covoar

On Tue, 3 Jul 2018, 04:32 Joel Sherrill, wrote: > > > On Mon, Jul 2, 2018 at 5:50 PM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> Hello, >> >> I wanted some help in understanding the >> function of the following files in c

Query regarding covoar

Hello, I wanted some help in understanding the function of the following files in covoar 1. qemu-dump-trace.c 2. CoverageReaderQEMU.cc 3. TraceConverter.cc If the information I'm seeking is already present in a documentation, the link to the doc would be helpful. :) Thanks --vijay

[PATCH v2] coverage : Add support to run coverage in supported bsp without extra options

Close #3440 --- tester/rt/test.py| 21 ++--- tester/rtems/testing/bsps/leon3-qemu-cov.ini | 1 + 2 files changed, 15 insertions(+), 7 deletions(-) diff --git a/tester/rt/test.py b/tester/rt/test.py index 9214ad6..029ee7c 100644 --- a/tester/rt/test.py

Re: [PATCH] coverage : Add support to run coverage in supported bsp without extra options

On 15 June 2018 at 08:38, Chris Johns wrote: > On 14/06/2018 03:12, Gedare Bloom wrote: > > On Wed, Jun 13, 2018 at 12:23 PM, Vijay Kumar Banerjee > > wrote: > >> On Wed, 13 Jun 2018, 21:39 Gedare Bloom, wrote: > >>> On Wed, Jun 13, 2018 at 11:58 A

Re: [PATCH] coverage : Add support to run coverage in supported bsp without extra options

On 24 June 2018 at 11:11, Chris Johns wrote: > On 24/06/2018 14:54, Chris Johns wrote: > > On 24/06/2018 12:35, Chris Johns wrote: > >> On 23/06/2018 05:10, Vijay Kumar Banerjee wrote: > >>> I'm running rtems-test with the following command > >>> >

[ GSoC coverage ] weekly project status update

Hello, This week I spent some time trying to build the leon3 bsp with -Os and -ftest-coverage options. I was getting a lot of errors with this, I tried to build with -O0 option, and it build properly. Gedare pointed in the last meeting that this might be an error with the compiler. I

Re: [PATCH] coverage : Add support to run coverage in supported bsp without extra options

On Tue, 19 Jun 2018, 08:54 Chris Johns, wrote: > On 19/06/2018 13:16, Vijay Kumar Banerjee wrote: > > I would like to get my 22 patches pushed to master before moving on > this topic. > > This is the report I generate: > > > > > https://ftp.rtems.org

Re: [PATCH] coverage : Add support to run coverage in supported bsp without extra options

On Tue, 19 Jun 2018, 05:32 Chris Johns, wrote: > On 16/06/2018 02:55, Vijay Kumar Banerjee wrote: > > On Fri, 15 Jun 2018, 08:39 Chris Johns, > <mailto:chr...@rtems.org>> wrote: > > On 14/06/2018 03:12, Gedare Bloom wrote: > > > On Wed, Jun 13, 20

Re: error while building from RSB

On 16 June 2018 at 01:50, Gedare Bloom wrote: > Hello there, > > someone on IRC mentions that www.gaisler.com works still. Maybe try > changing the URL to that one? > > https://www.gaisler.com/gdb/gdb-8.0.1-sis-leon2-leon3.diff returns 404 > On Fri, Jun 15, 2018 at 1:09 PM,

Re: error while building from RSB

On Fri, 15 Jun 2018, 22:35 Cillian O'Donnell, wrote: > > > On Fri, 15 Jun 2018 at 17:49, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> Hello, >> >> While trying to freshly build RTEMS from RSB with the following command >> >> `.

Re: [PATCH] coverage : Add support to run coverage in supported bsp without extra options

On Fri, 15 Jun 2018, 08:39 Chris Johns, wrote: > On 14/06/2018 03:12, Gedare Bloom wrote: > > On Wed, Jun 13, 2018 at 12:23 PM, Vijay Kumar Banerjee > > wrote: > >> On Wed, 13 Jun 2018, 21:39 Gedare Bloom, wrote: > >>> On Wed, Jun 13, 2018 at 11:58 A

error while building from RSB

Hello, While trying to freshly build RTEMS from RSB with the following command `../source-builder/sb-set-builder \ --prefix=/home/lunatic/development/rtems/5 5/rtems-sparc" I'm getting the following error : -- error: downloading https://gaisler.org/gdb/gdb-8.0.1-sis-leon2-leon3.diff:

Re: [PATCH] coverage : Add support to run coverage in supported bsp without extra options

On Wed, 13 Jun 2018, 21:39 Gedare Bloom, wrote: > On Wed, Jun 13, 2018 at 11:58 AM, Vijay Kumar Banerjee > wrote: > > On 13 June 2018 at 10:29, Gedare Bloom wrote: > >> > >> On Thu, Jun 7, 2018 at 7:08 AM, Vijay Kumar Banerjee > >> wrote: > >

Re: [PATCH] coverage : Add support to run coverage in supported bsp without extra options

On 13 June 2018 at 10:29, Gedare Bloom wrote: > On Thu, Jun 7, 2018 at 7:08 AM, Vijay Kumar Banerjee > wrote: > > Close #3440 > > --- > > tester/rt/coverage.py | 6 -- > > tester/rt/test.py | 15 ++- > > 2 files changed, 14 insertions(+

Re: error while building leon3 with gcov flags

On Wed, 13 Jun 2018, 11:51 Joel Sherrill, wrote: > > > On Sun, Jun 10, 2018, 6:02 PM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> >> >> On Sun, 10 Jun 2018, 20:52 Joel Sherrill, wrote: >> >>> >>> >>

Re: [PATCH] coverage : Add support to run coverage in supported bsp without extra options

; > On Tue, Jun 12, 2018, 8:39 AM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> Please review this patch. :) >> On 7 June 2018 at 16:38, Vijay Kumar Banerjee >> wrote: >> >>> Close #3440 >>> --- >>> tester/rt/cov

Re: [PATCH] coverage : Add support to run coverage in supported bsp without extra options

Please review this patch. :) On 7 June 2018 at 16:38, Vijay Kumar Banerjee wrote: > Close #3440 > --- > tester/rt/coverage.py | 6 -- > tester/rt/test.py | 15 ++- > 2 files changed, 14 insertions(+), 7 deletions(-) > > diff --git a/tester/rt/co

Re: error while building leon3 with gcov flags

le-multiprocessing \ >--enable-tests --enable-cxx --enable-maintainer-mode > > What was yours? > > > On Wed, Jun 6, 2018 at 9:40 AM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> Hello, >> >> I have added

Re: error while building leon3 with gcov flags

On Sun, 10 Jun 2018, 20:52 Joel Sherrill, wrote: > > > On Sat, Jun 9, 2018, 6:02 PM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 10 June 2018 at 04:16, Joel Sherrill wrote: >> >>> I suggest this because it is a work around for you.

Re: error while building leon3 with gcov flags

On 10 June 2018 at 01:28, Joel Sherrill wrote: > > > On Sat, Jun 9, 2018, 2:29 PM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 10 June 2018 at 00:55, Joel Sherrill wrote: >> >>> >>> >>> On Sat, Jun 9, 2018, 2:22 P

Re: error while building leon3 with gcov flags

On 10 June 2018 at 00:55, Joel Sherrill wrote: > > > On Sat, Jun 9, 2018, 2:22 PM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 9 June 2018 at 19:56, Joel Sherrill wrote: >> >>> >>> >>> On Sat, Jun 9, 2018, 6:01 A

Re: error while building leon3 with gcov flags

On 9 June 2018 at 19:56, Joel Sherrill wrote: > > > On Sat, Jun 9, 2018, 6:01 AM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> Hello, >> >> I was going through the gcc manual for gcov >> https://gcc.gnu.org/onlinedocs/gcc/Gcov-an

Re: error while building leon3 with gcov flags

] Error 1 gmake[1]: Leaving directory '/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c' gmake: *** [Makefile:414: all-recursive] Error 1 = On 8 June 2018 at 01:13, Vijay Kumar Banerjee wrote: > > > On Fri, 8 Jun 2018, 01:09 Joel Sherrill, wrote: >

Re: error while building leon3 with gcov flags

gt; Will try to do that if possible. > > On Thu, Jun 7, 2018 at 2:29 PM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> Hello, >> >> I was looking into the code in GcovData.cc to see how it works >> and what it's doing, too me it looked l

Re: error while building leon3 with gcov flags

to work? Or something like a flow diagram? -- vijay On 7 June 2018 at 02:56, Vijay Kumar Banerjee wrote: > > > On Thu, 7 Jun 2018, 02:39 Joel Sherrill, wrote: > >> >> >> On Wed, Jun 6, 2018, 3:56 PM Vijay Kumar Banerjee < >> vijaykumar9...@gmail.com> w

[PATCH] coverage : Add support to run coverage in supported bsp without extra options

Close #3440 --- tester/rt/coverage.py | 6 -- tester/rt/test.py | 15 ++- 2 files changed, 14 insertions(+), 7 deletions(-) diff --git a/tester/rt/coverage.py b/tester/rt/coverage.py index 54933d5..af24124 100644 --- a/tester/rt/coverage.py +++ b/tester/rt/coverage.py @@

Re: error while building leon3 with gcov flags

On Thu, 7 Jun 2018, 02:39 Joel Sherrill, wrote: > > > On Wed, Jun 6, 2018, 3:56 PM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 7 June 2018 at 01:48, Joel Sherrill wrote: >> >>> >>> >>> On Wed, Jun 6, 2018, 2:07 P

Re: error while building leon3 with gcov flags

On 7 June 2018 at 01:48, Joel Sherrill wrote: > > > On Wed, Jun 6, 2018, 2:07 PM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 6 June 2018 at 20:49, Joel Sherrill wrote: >> >>> I can't duplicate this. My configure command was: >&g

Re: error while building leon3 with gcov flags

ble to open libscore_a-chain.gcno Processing file: libscore_a-chainnodecount.gcno . . . == > > On Wed, Jun 6, 2018 at 9:40 AM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> Hello, >> >> I have added the following changes in the bsps/s

error while building leon3 with gcov flags

Hello, I have added the following changes in the bsps/sparc/leon3/config/leon3.cfg -- CFLAGS_OPTIMIZE_V = -Os -g CFLAGS_OPTIMIZE_V += -ftest-coverage --- While trying to build with these flags, I got a bunch of the following errors: == {standard input}: Assembler messages:

Re: [PATCH v3] tester: Add script to generate html coverage report from covoar output

On 6 June 2018 at 17:48, Joel Sherrill wrote: > > > On Wed, Jun 6, 2018, 1:16 AM Cillian O'Donnell > wrote: > >> >> >> On Wed, 6 Jun 2018, 01:52 Joel Sherrill, wrote: >> >>> >>> >>> On Tue, Jun 5, 2018, 7:22 PM Vijay Kumar Baner

Re: [PATCH] Generate coverage analysis Report

On Wed, 6 Jun 2018, 08:31 Joel Sherrill, wrote: > > > On Tue, Jun 5, 2018, 9:54 PM Chris Johns wrote: > >> >> On 31/5/18 6:44 am, Vijay Kumar Banerjee wrote: >> > On 31 May 2018 at 02:02, Joel Sherrill > j...@rtems.org>> >> > wrote: >> &g

Re: [PATCH v3] tester: Add script to generate html coverage report from covoar output

On Wed, 6 Jun 2018, 06:22 Joel Sherrill, wrote: > > > On Tue, Jun 5, 2018, 7:22 PM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 6 June 2018 at 03:57, Joel Sherrill wrote: >> >>> I think everything is pushed. Is there a

Re: [PATCH v3] tester: Add script to generate html coverage report from covoar output

On 6 June 2018 at 03:57, Joel Sherrill wrote: > I think everything is pushed. Is there any patch outstanding? > > Thank you. No outstanding patch, everything on my side is squashed into it. :) > On Mon, Jun 4, 2018 at 3:44 PM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.co

[PATCH v3] tester: Add script to generate html coverage report from covoar output

Add support in tester to run covoar and generate an html report to display the summary of the coverage reports generated from covoar. Co-authored-by : Cillian O'Donnell --- .gitignore| 1 + tester/rt/coverage.py | 385

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

On 5 June 2018 at 01:28, Cillian O'Donnell wrote: > > > On 4 June 2018 at 20:29, Vijay Kumar Banerjee > wrote: > >> On 5 June 2018 at 00:51, Joel Sherrill wrote: >> >>> >>> >>> On Mon, Jun 4, 2018 at 2:12 PM, Vijay Kumar Banerjee < >

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

On 5 June 2018 at 00:51, Joel Sherrill wrote: > > > On Mon, Jun 4, 2018 at 2:12 PM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 5 June 2018 at 00:31, Joel Sherrill wrote: >> >>> I will add that covoar was originally design

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

needed. If we're headed in that way then I think making separate report.html like leon3-report.html would be simpler to achieve, and then create a master index.html for listing all the report htmls. > > On Mon, Jun 4, 2018 at 1:43 PM, Cillian O'Donnell > wrote: > >> >> >

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

On 2 June 2018 at 01:00, Vijay Kumar Banerjee wrote: > On 2 June 2018 at 00:48, Joel Sherrill wrote: > >> >> >> On Fri, Jun 1, 2018, 11:21 AM Vijay Kumar Banerjee < >> vijaykumar9...@gmail.com> wrote: >> >>> On 1 June 2018 at 20:30, Gedare Blo

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

On 2 June 2018 at 00:48, Joel Sherrill wrote: > > > On Fri, Jun 1, 2018, 11:21 AM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 1 June 2018 at 20:30, Gedare Bloom wrote: >> >>> On Fri, Jun 1, 2018 at 10:28 AM, Vijay Kumar Banerjee

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

On 1 June 2018 at 20:30, Gedare Bloom wrote: > On Fri, Jun 1, 2018 at 10:28 AM, Vijay Kumar Banerjee > wrote: > > On 1 June 2018 at 19:24, Joel Sherrill wrote: > >> > >> > >> > >> On Fri, Jun 1, 2018 at 2:46 AM, Vijay Kumar Banerjee &

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

On 1 June 2018 at 19:24, Joel Sherrill wrote: > > > On Fri, Jun 1, 2018 at 2:46 AM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> Here's the list of Ideas for improvements: >> >> 1. Include the section coverage in the bsp config f

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

rt of your GSoC. > > --joel > > On Thu, May 31, 2018 at 5:18 PM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> >> >> On Fri, 1 Jun 2018, 03:40 Joel Sherrill, wrote: >> >>> >>> >>> On Thu, May 31, 2018 at 4:57

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

On Fri, 1 Jun 2018, 03:40 Joel Sherrill, wrote: > > > On Thu, May 31, 2018 at 4:57 PM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 1 June 2018 at 02:50, Joel Sherrill wrote: >> >>> >>> >>> On Thu, May 31, 20

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

On 1 June 2018 at 02:50, Joel Sherrill wrote: > > > On Thu, May 31, 2018 at 4:15 PM, Cillian O'Donnell > wrote: > >> >> >> On Thu, 31 May 2018, 22:03 Vijay Kumar Banerjee, < >> vijaykumar9...@gmail.com> wrote: >> >>> On 1 June 2018 a

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

> sets, probably renamed to --coverage-sets=... Or require sets to be > chosen > > --coverage-sets=all or specific sets --coverage-sets=score,sapi,core > > > Yes, and it should work for more than 1 or 2. > > It can work for any number of sets. > > On Thu, 31 May 2018,

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

Thu, 31 May 2018, 21:29 Vijay Kumar Banerjee, > wrote: > >> On 1 June 2018 at 01:57, Cillian O'Donnell wrote: >> >>> So is it checking whether it's --coverage or --coverage=set1,set2? Are >>> those the 2 possibilities your checking? >>> >>

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

On 1 June 2018 at 01:19, Gedare Bloom wrote: > On Thu, May 31, 2018 at 3:47 PM, Vijay Kumar Banerjee > wrote: > > On 1 June 2018 at 01:07, Cillian O'Donnell > wrote: > >> > >> > >> > >> On 31 May 2018 at 19:07, Vijay Kumar Banerjee > >

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

On 1 June 2018 at 01:07, Cillian O'Donnell wrote: > > > On 31 May 2018 at 19:07, Vijay Kumar Banerjee > wrote: > >> Add support in tester to run covoar and generate an html report to display >> the summary of the coverage reports generated from covoar. >> >

[PATCH v2] tester: Add script to generate html coverage report from covoar output

Add support in tester to run covoar and generate an html report to display the summary of the coverage reports generated from covoar. Co-authored-by : Cillian O'Donnell --- tester/rt/coverage.py | 379 ++ tester/rt/test.py

Generating separate coverage reports for different symbol-sets from covoar

Hello, The covoar currently is capable of processing multisets from the symbol-sets ini file, however, it currently keeps all the reports in the same directory (../coverage/score). Before the recent updates to covoar it could only read one set/subsystem from an ini file, and the script used to

Re: [PATCH] Generate coverage analysis Report

On 31 May 2018 at 02:02, Joel Sherrill wrote: > > > On Wed, May 30, 2018 at 3:29 PM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 31 May 2018 at 00:28, Joel Sherrill wrote: >> >>> >>> >>> I may not understand c

Re: [PATCH] Generate coverage analysis Report

On 31 May 2018 at 00:28, Joel Sherrill wrote: > > > I may not understand correctly but there is test_run and coverage_run. > Someone > suggested making coverage_running an option to test_run. If that's what's > being > asked for, then I think doing it in a follow up patch is OK. > > If that's

Re: [PATCH] Generate coverage analysis Report

On 30 May 2018 at 23:29, Joel Sherrill wrote: > > > On Wed, May 30, 2018 at 12:54 PM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 30 May 2018 at 22:51, Gedare Bloom wrote: >> >>> Please provide your name in your commits (git

<    3   4   5   6   7   8   9   10   >