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

2018 at 13:30, Vijay Kumar Banerjee <vijaykumar9...@gmail.com> wrote: > > On 6 May 2018 at 13:29, Chris Johns <chr...@rtems.org> wrote: > >> On 6/5/18 5:28 pm, Vijay Kumar Banerjee wrote: >> >>> On 6 May 2018 at 08:54, Chris Johns <chr...@rtems.org >&

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 <chr...@rtems.org> wrote: > On 6/5/18 5:28 pm, Vijay Kumar Banerjee wrote: > >> On 6 May 2018 at 08:54, Chris Johns <chr...@rtems.org > chr...@rtems.org>> wrote: >> >> Would you please try `waf clean build`

Re: rtems-tools: coverage covoar GSoC merge

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

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

On 14 May 2018 at 12:10, Cillian O'Donnell <cpodonne...@gmail.com> wrote: > > > On Sun, 13 May 2018, 22:15 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com> > wrote: > >> On 14 May 2018 at 02:15, Cillian O'Donnell <cpodonne...@gmail.com> wrote: >&

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 23:37, Joel Sherrill <j...@rtems.org> 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 <j...@rtems.org> wrote: >> >>>

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

On Mon, 14 May 2018, 23:24 Cillian O'Donnell, <cpodonne...@gmail.com> wrote: > > > On Mon, 14 May 2018, 09:50 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com> > wrote: > >> On 14 May 2018 at 12:10, Cillian O'Donnell <cpodonne...@gmail.com> wrote: >>

Re: gcov support in Covoar

On 14 May 2018 at 21:21, Joel Sherrill <j...@rtems.org> 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

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

O'Donnell <cpodonne...@gmail.com> >> >> Add ability to organize symbol sets of libraries in INI file >> and then read them with covoar and load the symbols directly from the >> libraries. >> >> rtems-tools/../testing: Add configuration files for coverage ana

replying to mailing list

I have a bit off topic question . I receive devel Digests from the devel mailing list, how do I reply to a particular message in the mailing list without breaking the thread? -- vijay ___ devel mailing list devel@rtems.org

Re: replying to mailing list

> Hello Vijay, > > when you first registered, you should have received a mail with a > password that you can use here: > > https://lists.rtems.org/mailman/listinfo/devel > > By the way: It's not 100% correct that you can't reply without breaking > a thread. But it involves manipulating mail

Re: replying to mailing list

Ok, thanks. Can you please also tell ne how to switch ? is it by subscribing to the list again and selecting no in the daily digest option ? On Sat, 28 Apr 2018, 17:49 Joel Sherrill, <j...@rtems.org> wrote: > > > On Sat, Apr 28, 2018, 8:05 AM Vijay Kumar Banerjee < > vij

Re: replying to mailing list

Thanks , I found it . On Sat, 28 Apr 2018, 18:02 Joel Sherrill, <j...@rtems.org> wrote: > > > On Sat, Apr 28, 2018, 8:23 AM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> Ok, thanks. Can you please also tell ne how to switch ? >>

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

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

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

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

On Fri, 11 May 2018, 02:19 Cillian O'Donnell, <cpodonne...@gmail.com> wrote: > > > On 10 May 2018 at 20:15, Vijay Kumar Banerjee <vijaykumar9...@gmail.com> > wrote: > >> Frankly, I'm totally confused at the moment. I'm not able to come up with >> a

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

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

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

On Sun, 13 May 2018, 18:24 Cillian O'Donnell, <cpodonne...@gmail.com> wrote: > > > On 13 May 2018 at 13:47, Vijay Kumar Banerjee <vijaykumar9...@gmail.com> > wrote: > >> >> On Sun, 13 May 2018, 18:14 Cillian O'Donnell, <cpodonne...@gmail.com> >

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

not > 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 <vijaykumar9...@gmail.com> > 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, 16:15 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com> wrote: > > > On Sun, 13 May 2018, 16:09 Cillian O'Donnell, <cpodonne...@gmail.com> > wrote: > >> It does seem to be having some knock on effect. Covoar made it past these >> checks b

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

On Sun, 13 May 2018, 18:24 Cillian O'Donnell, <cpodonne...@gmail.com> wrote: > > > On 13 May 2018 at 13:47, Vijay Kumar Banerjee <vijaykumar9...@gmail.com> > wrote: > >> >> On Sun, 13 May 2018, 18:14 Cillian O'Donnell, <cpodonne...@gmail.com> >

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

On 13 May 2018 at 16:16, Vijay Kumar Banerjee <vijaykumar9...@gmail.com> wrote: > > > On Sun, 13 May 2018, 16:15 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com> > wrote: > >> >> >> On Sun, 13 May 2018, 16:09 Cillian O'Donnell, <cpodonne...@gmail

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

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

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

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

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

Re: How to download the required tar file?

y 11, 2018 at 1:37 PM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> >> >> On Fri, 11 May 2018, 23:59 Danxue Huang, <danxue.hu...@gmail.com> wrote: >> >>> Hey Vijay, >>> >>> Thank you so much for answering my ques

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

Re: How to download the required tar file?

to run hello world ? > > Best, > Dannie > > On Fri, May 11, 2018 at 12:57 PM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> >> Hello Dannie, >> >> I guess you're looking for the testsuites direcotry under the build >> d

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

On Fri, 11 May 2018, 01:09 Joel Sherrill, <j...@rtems.org> 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

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

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, <j...@rtems.org> 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

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

8 at 15:40, Joel Sherrill <j...@rtems.org> 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 >>> >>

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

imple. We 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 <j...@rtems.org> 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 <chr...@rtems.org> 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 >> chr...@rtems.org>> >>

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

On 6 May 2018 at 03:05, Chris Johns <chr...@rtems.org> wrote: > > On 6 May 2018, at 7:04 am, Vijay Kumar Banerjee <vijaykumar9...@gmail.com> > wrote: > > > On 6 May 2018 at 02:25, Cillian O'Donnell <cpodonne...@gmail.com> wrote: > >> >> >&

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.

rtems-tools/build/tester/covoar/CoverageReaderQEMU.cc.1.o'] On 5 May 2018 at 21:47, Joel Sherrill <j...@rtems.org> wrote: > > > On Sat, May 5, 2018, 10:57 AM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> Hello, >> >> I'm getting t

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

On Fri, 18 May 2018, 11:52 Cillian O'Donnell, <cpodonne...@gmail.com> wrote: > > > On Thu, 17 May 2018, 21:32 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com> > wrote: > >> hello, >> >> I have attached the html report ! >> > > Report looks

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

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 >

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

On 19 May 2018 at 17:56, Vijay Kumar Banerjee <vijaykumar9...@gmail.com> wrote: > On 19 May 2018 at 17:50, Vijay Kumar Banerjee <vijaykumar9...@gmail.com> > wrote: > >> On 19 May 2018 at 17:44, Cillian O'Donnell <cpodonne...@gmail.com> wrote: >> >>>

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

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

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

On Sun, 20 May 2018, 01:56 Cillian O'Donnell, <cpodonne...@gmail.com> wrote: > > > On Sat, 19 May 2018, 20:59 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com> > wrote: > >> Hello, >> >> My end sem exams are starting next week from 22nd May and w

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

[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

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

On 19 May 2018 at 18:28, Cillian O'Donnell <cpodonne...@gmail.com> wrote: > > > On Sat, 19 May 2018, 13:28 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com> > wrote: > >> On 19 May 2018 at 17:56, Vijay Kumar Banerjee <vijaykumar9...@gmail.com> >> wrote

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

On 20 May 2018 at 00:53, Vijay Kumar Banerjee <vijaykumar9...@gmail.com> wrote: > > > On Sun, 20 May 2018, 00:45 Cillian O'Donnell, <cpodonne...@gmail.com> > wrote: > >> It works.. Sorry I was using the right covoar but the wrong rtems-test. >> Ahh its n

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

On 21 May 2018 at 02:29, Cillian O'Donnell <cpodonne...@gmail.com> wrote: > > > On Sun, 20 May 2018, 15:35 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com> > wrote: > >> On 20 May 2018 at 00:53, Vijay Kumar Banerjee <vijaykumar9...@gmail.com> >> wro

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.

On 21 May 2018 at 21:42, Joel Sherrill <j...@rtems.org> 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 <j...@rtems.org> wrote: >> >>> >>

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

On 21 May 2018 at 20:37, Joel Sherrill <j...@rtems.org> 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 <j...@rtems.org> wrote: >> >>>

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

gt; On Mon, May 21, 2018, 6:35 AM Cillian O'Donnell <cpodonne...@gmail.com> > 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 &

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

On 21 May 2018 at 11:56, Cillian O'Donnell <cpodonne...@gmail.com> wrote: > > > On Sun, 20 May 2018, 22:33 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com> > wrote: > >> On 21 May 2018 at 02:29, Cillian O'Donnell <cpodonne...@gmail.com> wrote: >> >&

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

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

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

On 22 May 2018 at 00:33, Joel Sherrill <j...@rtems.org> 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 <j...@rtems.org> wrote: >> >>> >&

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

On 21 May 2018 at 23:07, Joel Sherrill <j...@rtems.org> 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 <j...@rtems.org> wrote: >> >>> >>

Re: Covoar address to line to DWARF updates.

On Fri, 25 May 2018, 09:26 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com> wrote: > > > On Fri, 25 May 2018, 02:52 Chris Johns, <ch...@contemporary.net.au> wrote: > >> On 25/5/18 7:11 am, Vijay Kumar Banerjee wrote: >> > On Fri, 25 May 2018, 00:35 Joel S

Re: Covoar address to line to DWARF updates.

On 24 May 2018 at 18:58, Vijay Kumar Banerjee <vijaykumar9...@gmail.com> wrote: > On 24 May 2018 at 18:21, Gedare Bloom <ged...@rtems.org> wrote: > >> Vijay, >> >> Please test Chris' modifications. >> >> On Thu, May 24, 2018 at 2:23 AM, Chris John

Re: Covoar address to line to DWARF updates.

On Fri, 25 May 2018, 00:35 Joel Sherrill, <j...@rtems.org> 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 <vijaykumar9...@gmail.com> >> wrote:

Re: Covoar address to line to DWARF updates.

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

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

On 18 May 2018 at 19:09, Cillian O'Donnell <cpodonne...@gmail.com> wrote: > > > On Fri, 18 May 2018, 12:36 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com> > wrote: > >> >> On 18 May 2018 at 12:30, Cillian O'Donnell <cpodonne...@gmail.com> wrote: &

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

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

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

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

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.

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

On 19 May 2018 at 03:29, Joel Sherrill <j...@rtems.org> 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, <j...@rtems.org> wrote: >>

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

On Sat, 19 May 2018, 03:06 Joel Sherrill, <j...@rtems.org> 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 <vijaykumar9...@gmail.com> >> w

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

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

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

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

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

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

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

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 2018, 16:5

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 =

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

  1   2   3   4   5   6   7   8   9   10   >