Re: [PATCH] covoar: Add symbol set reader and ELF data parser to covoar.

This is the log file that I'm getting after running the test I'm getting a lot of 'invalid' results , am I missing something ? after this patch along with with the c++ cleanup patch, we have to start working on parsing the coverage right? RTEMS Testing - Tester, 5 (0e93af6a88b8 modified) Comman

Re: [PATCH] covoar: Add symbol set reader and ELF data parser to covoar.

On Sun, 29 Apr 2018, 03:57 Cillian O'Donnell, wrote: > > > On Sat, 28 Apr 2018, 20:39 Vijay Kumar Banerjee, > wrote: > >> >> This is the log file that I'm getting after running the test >> >> I'm getting a lot of 'invalid' resu

Re: rtems-tools: coverage covoar GSoC merge

Hello, I want to ask some things about the project to get a clear understanding of the objectives/milestones and current status of the project. I also seek advice on my Tasks/obectives. 1. The covoar has been updated to read symbols from the library and the next milestone is to remove covoar's de

Re: rtems-tools: coverage covoar GSoC merge

On 3 May 2018 at 22:58, Cillian O'Donnell wrote: > > > On Thu, 3 May 2018, 16:23 Vijay Kumar Banerjee, > wrote: > >> Hello, >> >> I want to ask some things about the project to get a clear understanding >> of the objectives/milestones and current sta

Re: rtems-tools: coverage covoar GSoC merge

On 4 May 2018 at 04:34, Joel Sherrill wrote: > > > On Thu, May 3, 2018 at 1:45 PM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> >> On 3 May 2018 at 22:58, Cillian O'Donnell wrote: >> >>> >>> >>> On Thu,

Re: rtems-tools: coverage covoar GSoC merge

On Fri, 4 May 2018, 12:17 Cillian O'Donnell, wrote: > > > On Fri, 4 May 2018, 00:04 Joel Sherrill, wrote: > >> >> >> On Thu, May 3, 2018 at 1:45 PM, Vijay Kumar Banerjee < >> vijaykumar9...@gmail.com> wrote: >> >>> >>> On 3

Re: [PATCH 2/4] covoar: Use DWARF to map addresses to source files and lines.

Hello, I'm getting this build failure after applying this patch --- Build failed -> task in 'ccovoar' failed with exit status 1: {task 140086064254560: cxx app_common.cc -> app_common.cc.1.o} ['/usr/bin/g++', '-std=c++11', '-O2', '-g', '-Itester/covoar', '-I../tester/covoar', '-Irtemstoolkit', '

Re: [PATCH 2/4] covoar: Use DWARF to map addresses to source files and lines.

27;ccovoar' failed with exit status 1: {task 140568634392736: cxx CoverageReaderQEMU.cc -> CoverageReaderQEMU.cc.1.o} ['/usr/bin/g++', '-std=c++11', '-O2', '-g', '-Itester/covoar', '-I../tester/covoar', '-Irtemstoolkit', &#x

Re: [PATCH 2/4] covoar: Use DWARF to map addresses to source files and lines.

On 6 May 2018 at 02:25, Cillian O'Donnell wrote: > > > On 5 May 2018 at 21:12, Chris Johns wrote: > >> >> >> > On 6 May 2018, at 2:44 am, Joel Sherrill wrote: >> > >> > Looks similar to Cillian's failure. Chris will have to show me where >> libdwarf comes from. It needs to be supplied with RTEM

Re: [PATCH 2/4] covoar: Use DWARF to map addresses to source files and lines.

On 6 May 2018 at 03:05, Chris Johns wrote: > > On 6 May 2018, at 7:04 am, Vijay Kumar Banerjee > wrote: > > > On 6 May 2018 at 02:25, Cillian O'Donnell wrote: > >> >> >> On 5 May 2018 at 21:12, Chris Johns wrote: >> >>>

Fwd: [PATCH 2/4] covoar: Use DWARF to map addresses to source files and lines.

On 6 May 2018 at 08:54, Chris Johns wrote: > On 6/5/18 9:49 am, Chris Johns wrote: > >> On 6/5/18 7:54 am, Vijay Kumar Banerjee wrote: >> >>> On 6 May 2018 at 03:05, Chris Johns >> chr...@rtems.org>> >>> wrote: >>> >>> C

Re: Fwd: [PATCH 2/4] covoar: Use DWARF to map addresses to source files and lines.

On 6 May 2018 at 13:29, Chris Johns wrote: > On 6/5/18 5:28 pm, Vijay Kumar Banerjee wrote: > >> On 6 May 2018 at 08:54, Chris Johns > chr...@rtems.org>> wrote: >> >> Would you please try `waf clean build` to see if rebuilding >> everyth

Re: Fwd: [PATCH 2/4] covoar: Use DWARF to map addresses to source files and lines.

+= [rtemstoolkit + '/win32'] -- vijay On 7 May 2018 at 13:30, Vijay Kumar Banerjee wrote: > > On 6 May 2018 at 13:29, Chris Johns wrote: > >> On 6/5/18 5:28 pm, Vijay Kumar Banerjee wrote: >> >>> On 6 May 2018 at 08:54, Chris Johns >> chr..

Re: Fwd: [PATCH 2/4] covoar: Use DWARF to map addresses to source files and lines.

On Mon, 7 May 2018, 20:10 Joel Sherrill, wrote: > > > On Mon, May 7, 2018 at 6:01 AM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> I have added the path to libdwarf here >> > > That worked for me to build but not to link. > > I

Re: Fwd: [PATCH 2/4] covoar: Use DWARF to map addresses to source files and lines.

y 2018 at 15:40, Joel Sherrill wrote: > >> >> >> On Mon, May 7, 2018 at 6:01 AM, Vijay Kumar Banerjee < >> vijaykumar9...@gmail.com> wrote: >> >>> I have added the path to libdwarf her

Re: Fwd: [PATCH 2/4] covoar: Use DWARF to map addresses to source files and lines.

just need to hear from Chris. > > --joel > This will hopefully fix it, unfortunately I can't test it now, as I'm on mobile. Hopefully Cillian can try building with the diff applied. > > > On Mon, May 7, 2018 at 12:42 PM, Joel Sherrill wrote: > >> >

Re: Fwd: [PATCH 2/4] covoar: Use DWARF to map addresses to source files and lines.

On 8 May 2018 at 00:33, Cillian O'Donnell wrote: > Here's the branch with work in progress for the tester. Have a look when > you can Vijay. > > https://github.com/cillianodonnell/rtems-tools/tree/tester-support > > > I am going through this now. according to your last commit message, the qemu.cf

Re: V2 Add DWARF support to the rtemstoolkit and put it to use.

Frankly, I'm totally confused at the moment. I'm not able to come up with a proper task list to serially go through. according to my understanding (and proposal), the major goals are: 1. Get the coverage analysis running again and get it merged with the current master repo. 2. Generating line cov

Re: V2 Add DWARF support to the rtemstoolkit and put it to use.

On 11 May 2018 at 00:09, Chris Johns wrote: > On 11/5/18 5:37 am, Cillian O'Donnell wrote: > > On Thu, 10 May 2018, 11:48 Chris Johns, > > > It is not a exception in an exception or in a stack unwind path, it > is an > > exception being thrown with no catch. > > > > The covoar `main(

Re: V2 Add DWARF support to the rtemstoolkit and put it to use.

On Fri, 11 May 2018, 01:09 Joel Sherrill, wrote: > > > On Thu, May 10, 2018 at 2:15 PM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> Frankly, I'm totally confused at the moment. I'm not able to come up with >> a proper task list to

Re: V2 Add DWARF support to the rtemstoolkit and put it to use.

On Fri, 11 May 2018, 02:19 Cillian O'Donnell, wrote: > > > On 10 May 2018 at 20:15, Vijay Kumar Banerjee > wrote: > >> Frankly, I'm totally confused at the moment. I'm not able to come up with >> a proper task list to serially go through. >> >

Re: How to download the required tar file?

Hello Dannie, I guess you're looking for the testsuites direcotry under the build directory. It can be found somewhere like this $HOME/development/rtems/kernel/erc32/sparc-rtems5/c/erc32/testsuites If you're looking for the c code then you can find it under the RTEMS_ROOT directory. In my set up

Re: How to download the required tar file?

n my machine, there are no such files like > "kernel", "erc32" and "testsuites", do you know why do I miss these files? > Or how can I get these files? Thank you! > maybe I didn't understand the current status of set up. are you trying to run hello wo

Re: How to download the required tar file?

miss these files? >>> Or how can I get these files? Thank you! >>> >> >> maybe I didn't understand the current status of set up. >> are you trying to run hello world ? >> >>> >>> Best, >>> Dannie >>> >>> On F

Re: V2 Add DWARF support to the rtemstoolkit and put it to use.

On 11 May 2018 at 11:50, Cillian O'Donnell wrote: > At the moment when the tester runs covoar the error messages generated are > a clear indicator of what is wrong, so task list is dictated by what > they're saying at the moment. Fixing the mismatch between exe.cov and .cov > is the next thing. T

Re: [PATCH] covoar: fixing the extension mismatch in trace file

On Sun, 13 May 2018, 10:09 Chris Johns, wrote: > Sorry for the post in the other thread. I did not see this one. > > On 13/5/18 9:28 am, Joel Sherrill wrote: > > > > > > On Sat, May 12, 2018 at 2:42 PM, thelunatic > > wrote: > > > > --- > > > > > > Every patc

Re: [PATCH] covoar: fixing the extension mismatch in trace file

On 13 May 2018 at 10:50, Chris Johns wrote: > On 13/5/18 4:44 pm, Vijay Kumar Banerjee wrote: > > On Sun, 13 May 2018, 10:09 Chris Johns, > <mailto:chr...@rtems.org>> wrote: > > > > > >Coverage::CoverageFormats_t coverageFormat = >

Re: [PATCH] covoar: fixing the extension mismatch in trace file

first one, that's one step . The next step can be solved by adding the path to the build-target , i.e. sparc-rtems5 , from HOME directory, you can manually add it and see it running for now. That tells us that inclusion of the path in more standard way will solve it . > > Maybe its

Re: [PATCH] covoar: fixing the extension mismatch in trace file

On Sun, 13 May 2018, 16:15 Vijay Kumar Banerjee, wrote: > > > On Sun, 13 May 2018, 16:09 Cillian O'Donnell, > wrote: > >> It does seem to be having some knock on effect. Covoar made it past these >> checks before. >> >> - >> Tota

Re: [PATCH] covoar: fixing the extension mismatch in trace file

On 13 May 2018 at 16:16, Vijay Kumar Banerjee wrote: > > > On Sun, 13 May 2018, 16:15 Vijay Kumar Banerjee, > wrote: > >> >> >> On Sun, 13 May 2018, 16:09 Cillian O'Donnell, >> wrote: >> >>> It does seem to be having some k

Re: [PATCH] covoar: fixing the extension mismatch in trace file

in > /home/cpod/development/rtems/leon3 > ***Cleaning tempfiles*** > > So there does seem to be some knock on effect of just tacking on .cov > there. Can't see all the consequences immediately but I'm having a look > now. I'll let you know if I find anything. > >

Re: [PATCH] covoar: fixing the extension mismatch in trace file

t > quite right but that's just collaborative development, you'll have to get > used to it :)... > That's alright. :) > > On 13 May 2018 at 12:39, Vijay Kumar Banerjee > wrote: > >> >> >> On Sun, 13 May 2018, 17:02 Cillian O'Donnell, >>

Re: [PATCH] covoar: fixing the extension mismatch in trace file

On Sun, 13 May 2018, 18:14 Cillian O'Donnell, wrote: > > > On 13 May 2018 at 13:35, Vijay Kumar Banerjee > wrote: > >> >> On Sun, 13 May 2018, 17:32 Cillian O'Donnell, >> wrote: >> >>> I understand but that's a separate issue. I c

Re: [PATCH] covoar: fixing the extension mismatch in trace file

On Sun, 13 May 2018, 18:24 Cillian O'Donnell, wrote: > > > On 13 May 2018 at 13:47, Vijay Kumar Banerjee > wrote: > >> >> On Sun, 13 May 2018, 18:14 Cillian O'Donnell, >> wrote: >> >>> >>> >>> On 13 May 2018 at 13:3

Re: [PATCH] covoar: fixing the extension mismatch in trace file

On Sun, 13 May 2018, 18:24 Cillian O'Donnell, wrote: > > > On 13 May 2018 at 13:47, Vijay Kumar Banerjee > wrote: > >> >> On Sun, 13 May 2018, 18:14 Cillian O'Donnell, >> wrote: >> >>> >>> >>> On 13 May 2018 at 13:3

Re: [PATCH] covoar: fixing the extension mismatch in trace file

On 13 May 2018 at 19:00, Cillian O'Donnell wrote: > Is there supposed to be a message there? > > Anyway just to clear this up, try this for me. > > 1. Grab a new branch of > > https://github.com/cillianodonnell/rtems-tools/tree/tester-support > > which is the current master plus one patch with th

Re: [PATCH] covoar: fixing the extension mismatch in trace file

On 13 May 2018 at 21:02, Vijay Kumar Banerjee wrote: > On 13 May 2018 at 19:00, Cillian O'Donnell wrote: > >> Is there supposed to be a message there? >> >> Anyway just to clear this up, try this for me. >> >> 1. Grab a new branch of >> >>

Re: [PATCH] covoar: fixing the extension mismatch in trace file

On 13 May 2018 at 21:05, Gedare Bloom wrote: > Probably this is because rtems-sparc5 does not have a . in it like > rtems-sparc4.11 > > > Does that really make the difference ? it is parsed by covoar/DesiredSymbols.cc , it just simply replaces the @BUILD-TARGET@ with the buildTarget _

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 14 May 2018 at 02:15, Cillian O'Donnell wrote: > --- > tester/covoar/covoar.cc | 10 +++--- > 1 file changed, 3 insertions(+), 7 deletions(-) > > diff --git a/tester/covoar/covoar.cc b/tester/covoar/covoar.cc > index 5c87402..c6b0589 100644 > --- a/tester/covoar/covoar.cc > +++ b/tester/c

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 14 May 2018 at 12:10, Cillian O'Donnell wrote: > > > On Sun, 13 May 2018, 22:15 Vijay Kumar Banerjee, > wrote: > >> On 14 May 2018 at 02:15, Cillian O'Donnell wrote: >> >>> --- >>> tester/covoar/covoar.cc | 10 +++--- >>&g

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

Re: gcov support in Covoar

On 14 May 2018 at 21:21, Joel Sherrill wrote: > > > On Mon, May 14, 2018 at 10:19 AM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> Hello, >> >> The coverage report is showing some data now (txt only). There is still >> some work ne

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On Mon, 14 May 2018, 23:24 Cillian O'Donnell, wrote: > > > On Mon, 14 May 2018, 09:50 Vijay Kumar Banerjee, > wrote: > >> On 14 May 2018 at 12:10, Cillian O'Donnell wrote: >> >>> >>> >>> On Sun, 13 May 2018, 22:15 Vijay Kumar Ban

Re: gcov support in Covoar

On 14 May 2018 at 23:37, Joel Sherrill wrote: > > > On Mon, May 14, 2018 at 12:43 PM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 14 May 2018 at 21:21, Joel Sherrill wrote: >> >>> >>> >>> On Mon, May 14, 2018 at 1

generating gcno files

Current status: The gcno files are needed to pass it as an argument to covoar to generate the gcov reports. the generation of the gcno file needs changing the gcc flags . reference link : https://gcc.gnu.org/onlinedocs/gcc/Gcov-Data-Files.html#Gcov-Data-Files -- vijay _

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

hello, I have attached the html report ! Well it looks good but I hardcoded the paths, at least that gave the proper idea of what exactly needs to be done. Now I understand why --rtems-builddir stayed there for a long time , it makes the job simple . Here's a point that needs discussion : 1. the

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On Fri, 18 May 2018, 11:52 Cillian O'Donnell, wrote: > > > On Thu, 17 May 2018, 21:32 Vijay Kumar Banerjee, > wrote: > >> hello, >> >> I have attached the html report ! >> > > Report looks good! Well done. Was that just for samples. Did the

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 18 May 2018 at 12:30, Cillian O'Donnell wrote: > Cool, you should run it for the full testsuite and take a look at that > report (takes a while.. around 575 tests) > >> >>> When I try to run the full testsuites it gives the following error . What could be causing this ? ---

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 18 May 2018 at 19:09, Cillian O'Donnell wrote: > > > On Fri, 18 May 2018, 12:36 Vijay Kumar Banerjee, > wrote: > >> >> On 18 May 2018 at 12:30, Cillian O'Donnell wrote: >> >> >>> Cool, you should run it for the full testsuite and

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 19 May 2018 at 01:30, Cillian O'Donnell wrote: > > > On Fri, 18 May 2018, 14:55 Vijay Kumar Banerjee, > wrote: > >> >> >> On 18 May 2018 at 19:09, Cillian O'Donnell wrote: >> >>> >>> >>> On Fri, 18 May 2018, 12:36 V

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 19 May 2018 at 02:29, Vijay Kumar Banerjee wrote: > On 19 May 2018 at 01:30, Cillian O'Donnell wrote: > >> >> >> On Fri, 18 May 2018, 14:55 Vijay Kumar Banerjee, < >> vijaykumar9...@gmail.com> wrote: >> >>> >>> >>> On

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On Sat, 19 May 2018, 03:06 Joel Sherrill, wrote: > > > On Fri, May 18, 2018 at 4:01 PM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 19 May 2018 at 02:29, Vijay Kumar Banerjee >> wrote: >> >>> On 19 May 2018 at 01:30, Cillian

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 19 May 2018 at 03:29, Joel Sherrill wrote: > > > On Fri, May 18, 2018 at 4:53 PM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> >> >> On Sat, 19 May 2018, 03:06 Joel Sherrill, wrote: >> >>> >>> >>>

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 19 May 2018 at 04:26, Joel Sherrill wrote: > If you run nm on some of the executables, do you see the > Is symbol? We need to.know its type. > I did this on the testsuites find -iname '*.exe' -exec nm -A '{}' \; | grep '\' which returned nothing . am I using the right command ? _

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 19 May 2018 at 16:47, Cillian O'Donnell wrote: > > God these messages again... at least I'm an expert in fixing these :) > Vijay I'm only seeing the headings in the report on my end using your > branch. How are you running it and from where? Is there any changes you > haven't pushed? > I'm rur

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 19 May 2018 at 17:50, Vijay Kumar Banerjee wrote: > On 19 May 2018 at 17:44, Cillian O'Donnell wrote: > >> >> >> On Sat, 19 May 2018, 12:28 Vijay Kumar Banerjee, < >> vijaykumar9...@gmail.com> wrote: >> >>> On 19 May 2018 at 16:4

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 19 May 2018 at 17:56, Vijay Kumar Banerjee wrote: > On 19 May 2018 at 17:50, Vijay Kumar Banerjee > wrote: > >> On 19 May 2018 at 17:44, Cillian O'Donnell wrote: >> >>> >>> >>> On Sat, 19 May 2018, 12:28 Vijay Kumar Banerjee, < >>

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 19 May 2018 at 18:28, Cillian O'Donnell wrote: > > > On Sat, 19 May 2018, 13:28 Vijay Kumar Banerjee, > wrote: > >> On 19 May 2018 at 17:56, Vijay Kumar Banerjee >> wrote: >> >>> On 19 May 2018 at 17:50, Vijay Kumar Banerjee >>> wr

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On Sun, 20 May 2018, 00:45 Cillian O'Donnell, wrote: > 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? > Great! so next is the parsing of the s

[GSoC coverage] Possibility of being less active due to exams.

Hello, My end sem exams are starting next week from 22nd May and will go till 31st May. During this period I will be less efficient. I understand that the project is in a crucial state and 10 days of inactivity is unacceptable so I will try my best to be as active as possible during the gaps betwe

Re: [GSoC coverage] Possibility of being less active due to exams.

On Sun, 20 May 2018, 01:56 Cillian O'Donnell, wrote: > > > On Sat, 19 May 2018, 20:59 Vijay Kumar Banerjee, > wrote: > >> Hello, >> >> My end sem exams are starting next week from 22nd May and will go till >> 31st May. During this period I will

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 20 May 2018 at 00:53, Vijay Kumar Banerjee wrote: > > > On Sun, 20 May 2018, 00:45 Cillian O'Donnell, > wrote: > >> 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 man

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 21 May 2018 at 02:29, Cillian O'Donnell wrote: > > > On Sun, 20 May 2018, 15:35 Vijay Kumar Banerjee, > wrote: > >> On 20 May 2018 at 00:53, Vijay Kumar Banerjee >> wrote: >> >>> >>> >>> On Sun, 20 May 2018, 00:45 Cillian

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 21 May 2018 at 11:56, Cillian O'Donnell wrote: > > > On Sun, 20 May 2018, 22:33 Vijay Kumar Banerjee, > wrote: > >> On 21 May 2018 at 02:29, Cillian O'Donnell wrote: >> >>> >>> >>> On Sun, 20 May 2018, 15:35 Vijay Kumar Ban

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 21 May 2018 at 16:39, Cillian O'Donnell wrote: > > > On Mon, 21 May 2018, 12:08 Cillian O'Donnell, > wrote: > >> >> >> On Mon, 21 May 2018, 11:49 Vijay Kumar Banerjee, < >> vijaykumar9...@gmail.com> wrote: >> >>> On 21

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

Mon, May 21, 2018, 6:35 AM Cillian O'Donnell > wrote: > >> >> >> On Mon, 21 May 2018, 12:18 Vijay Kumar Banerjee, < >> vijaykumar9...@gmail.com> wrote: >> >>> On 21 May 2018 at 16:39, Cillian O'Donnell >>> wrote: >>> >>

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 21 May 2018 at 20:37, Joel Sherrill wrote: > > > On Mon, May 21, 2018 at 9:52 AM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 21 May 2018 at 17:39, Joel Sherrill wrote: >> >>> CPU-rtems5-objdump >>> >>&g

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 21 May 2018 at 21:42, Joel Sherrill wrote: > > > On Mon, May 21, 2018 at 10:13 AM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 21 May 2018 at 20:37, Joel Sherrill wrote: >> >>> >>> >>> On Mon, May 21, 2018 at

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 21 May 2018 at 23:07, Joel Sherrill wrote: > > > On Mon, May 21, 2018, 12:01 PM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 21 May 2018 at 21:42, Joel Sherrill wrote: >> >>> >>> >>> On Mon, May 21, 2018 at 1

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 22 May 2018 at 00:33, Joel Sherrill wrote: > > > On Mon, May 21, 2018, 1:54 PM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 21 May 2018 at 23:07, Joel Sherrill wrote: >> >>> >>> >>> On Mon, May 21, 2018, 12:01 P

Re: Covoar address to line to DWARF updates.

On 24 May 2018 at 18:58, Vijay Kumar Banerjee wrote: > On 24 May 2018 at 18:21, Gedare Bloom wrote: > >> Vijay, >> >> Please test Chris' modifications. >> >> On Thu, May 24, 2018 at 2:23 AM, Chris Johns wrote: >> > Hi, >> > >>

Re: Covoar address to line to DWARF updates.

On Fri, 25 May 2018, 00:35 Joel Sherrill, wrote: > > > On Thu, May 24, 2018, 10:43 AM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 24 May 2018 at 18:58, Vijay Kumar Banerjee >> wrote: >> >>> On 24 May 2018 at 18:21, Gedare Blo

Re: Covoar address to line to DWARF updates.

On Fri, 25 May 2018, 02:52 Chris Johns, wrote: > On 25/5/18 7:11 am, Vijay Kumar Banerjee wrote: > > On Fri, 25 May 2018, 00:35 Joel Sherrill, > <mailto:j...@rtems.org>> wrote: > > On Thu, May 24, 2018, 10:43 AM Vijay Kumar Banerjee > > mailto

Re: Covoar address to line to DWARF updates.

On Fri, 25 May 2018, 09:26 Vijay Kumar Banerjee, wrote: > > > On Fri, 25 May 2018, 02:52 Chris Johns, wrote: > >> On 25/5/18 7:11 am, Vijay Kumar Banerjee wrote: >> > On Fri, 25 May 2018, 00:35 Joel Sherrill, > > <mailto:j...@rtems.org>> wrote: >

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

Hello, The support for letting users input specific symbols for coverage analysis is now working in my cov-tester-support branch https://github.com/thelunatic/rtems-tools/tree/cov-tester-support Please have a look into the code and test it. The user can input specific symbols with the --coverag

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On Mon, 28 May 2018, 00:32 Cillian O'Donnell, wrote: > > > On Sun, 27 May 2018, 19:59 Vijay Kumar Banerjee, > wrote: > >> Hello, >> >> The support for letting users input specific symbols >> for coverage analysis is now working in my >>

Re: [PATCH] covoar.cc: Correct build path checks for multiple executables.

On 28 May 2018 at 00:49, Joel Sherrill wrote: > It sounds like great progress is being made but this thread is very long > and I am losing track of what needs committing. > > We can start a new thread. :) > Plus there is Chris' work to merge as well. > > How close is everything to moving back to

Re: Coverage support for tester

On 30 May 2018 at 00:54, Joel Sherrill wrote: > > > On Tue, May 29, 2018 at 11:27 AM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> >> >> On Tue, 29 May 2018, 20:10 Joel Sherrill, wrote: >> >>> >>> >>> On

Re: Coverage support for tester

d, May 30, 2018 at 10:29 AM, Vijay Kumar Banerjee > wrote: > > On 30 May 2018 at 00:54, Joel Sherrill wrote: > >> > >> > >> > >> On Tue, May 29, 2018 at 11:27 AM, Vijay Kumar Banerjee > >> wrote: > >>> > >>> > >&g

Re: Coverage support for tester

On Wed, 30 May 2018, 22:42 Cillian O'Donnell, wrote: > > > On Wed, 30 May 2018, 16:58 Gedare Bloom, wrote: > >> On Wed, May 30, 2018 at 11:32 AM, Vijay Kumar Banerjee >> wrote: >> > On 30 May 2018 at 20:18, Gedare Bloom wrote: >> >> >>

Re: Coverage support for tester

On 30 May 2018 at 22:55, Cillian O'Donnell wrote: > > > On Wed, 30 May 2018, 18:15 Vijay Kumar Banerjee, > wrote: > >> >> >> On Wed, 30 May 2018, 22:42 Cillian O'Donnell, >> wrote: >> >>> >>> >>> On Wed, 30 May

Re: [PATCH] Generate coverage analysis Report

On 30 May 2018 at 22:51, Gedare Bloom wrote: > Please provide your name in your commits (git config --user.name "My > Name") that you submit. > > OK Noted :) > The first line of this commit, and therefore the email subject, is > overly vague. Provide a slightly more specific description. > On We

Re: [PATCH] Generate coverage analysis Report

On 30 May 2018 at 22:51, Gedare Bloom wrote: > > +def coverage_run(opts, coverage, executables): > > +coverage.executables = executables > > +coverage.run() > > + > > def run(command_path = None): > > import sys > > tests = [] > > @@ -221,15 +228,16 @@ def run(command_path = No

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

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 the

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

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 lo

[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

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

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:57, Cillian O'Donnell wrote: > So is it checking whether it's --coverage or --coverage=set1,set2? Are > those the 2 possibilities your checking? > > Yes, right. :) > On Thu, 31 May 2018, 20:52 Vijay Kumar Banerjee, > wrote: > >> On 1 Ju

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

ge=set1,set2.... > On 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

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

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 201

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

re part 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

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 file.

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

<    1   2   3   4   5   6   7   8   9   10   >