Hello, My name is Anmol, I am a Google Summer of Code,
Student developer aspirant for 2020.
I have completed the Hello-world task.
I am interested in Ticket #2920 i.e "Improve Coverage Analysis Toolset". I
know that Dr. Joel is the owner and Dr. Gedare has reported it. Is there
What's the full output and what did you change in the time in between
having the same output that I posted and the new one?
Start a new thread for this issue like Chris mentioned.
On Tue, 3 Apr 2018, 20:35 Vijay Kumar Banerjee,
wrote:
>
>
>
>
> On 3 April 2018 at 03:58, Chris Johns wrote:
>
>>
On 3 April 2018 at 03:58, Chris Johns wrote:
> On 03/04/2018 02:10, Cillian O'Donnell wrote:
> > Sure if you want to crack at it.
> >
> > If you pull the ini-update branch again, I've included the other files
> you'll need.
> >
> > Now if you try and run rtems-test with coverage you will get
> >
On 03/04/2018 02:10, Cillian O'Donnell wrote:
> Sure if you want to crack at it.
>
> If you pull the ini-update branch again, I've included the other files you'll
> need.
>
> Now if you try and run rtems-test with coverage you will get
>
> cpod@cpod ~ $ $HOME/development/rtems/test/rtems-tools/
Sure if you want to crack at it.
If you pull the ini-update branch again, I've included the other files
you'll need.
Now if you try and run rtems-test with coverage you will get
cpod@cpod ~ $ $HOME/development/rtems/test/rtems-tools/tester/rtems-test
--rtems-tools=$HOME/development/rtems/5 --log
Hello ,
I'm currently going through the coverage code , Can you please help me
understand what are the specific changes that are needed for the coverage
to be running again?
thanks
-- vijay
On 26 March 2018 at 09:30, Vijay Kumar Banerjee
wrote:
> 1. Yes , I plan to work on identifying the disc
1. Yes , I plan to work on identifying the discrepancies between what
covoar reports directly and what the gcov reports based on its gcov output.
2. I understand this point that the scripting that generates symbol set
file, needs to be modified accordingly
3. I have planned to make a note and un
Just a couple of questions and planning issues. The planning issues
are because the requirements for some of the work are likely not solid
on our side.
1. Do you plan to work on identifying the discrepancies between
what covoar reports directly and what gcov reports based on its
gcov file output?
submitted !
If you find time , please give final review as well.
Thanks
On 26 Mar 2018 1:44 a.m., "Joel Sherrill" wrote:
> I am out and not at a computer. Someone can double check me but I believe
> you can replace the PDF you upload.
>
> Unless someone answers soon, just upload it.
>
> --joel
I am out and not at a computer. Someone can double check me but I believe
you can replace the PDF you upload.
Unless someone answers soon, just upload it.
--joel
On Mar 25, 2018 2:37 PM, "Vijay Kumar Banerjee"
wrote:
> It's the last day before the deadline!
> Please provide a final review of t
It's the last day before the deadline!
Please provide a final review of the proposal before submitting.
Thanks
-- vijay
On 24 March 2018 at 21:37, Vijay Kumar Banerjee
wrote:
> hello mentors and other developers of the community , there are only three
> days remaining to the GSoC proposal subm
hello mentors and other developers of the community , there are only three
days remaining to the GSoC proposal submission deadline.
I request the mentors and everyone in the community who has experience in
RTEMS, to please go through my proposal for Coverage Analysis tool
improvement project , if
Glad you have tests running. Hopefully as Cillian suggested, you can fix the
remaining issues to see coverage.
We certainly need to get this merged if Chris is OK with it and it doesn't
break anything else.
I am reviewing proposals now. Seems to be a queue. :)
--joel
On Wed, Mar 21, 2018 at 4:4
Sir ,
I have done the changes in the proposal , based on the comments in the
google doc , please review it and suggest any further changes if required
Thank you ,
-- vijay
P.S : the previous version is in parentheses , I will remove them after you
review the changes .
On 18 March 2018 at 16:05,
Thanks Cillian :)
It's great to see it running , I'll do some background reading about RSB,
and RTEMS-Tools along with the covoar code . And also work on my python
skills.
to try rtems-test on a bsp that runs gdb , I tried it on erc32 and that
also worked.
I'm also waiting for Joel and other me
On 18 March 2018 at 06:51, Vijay Kumar Banerjee
wrote:
> I guess I couldn't understand properly what you're suggesting ,
> on the basis of what I understood ,
> I have set the PATH like this
> /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/luna
> tic/.local/bin:/home/lunatic/bin
>
I thi
On 18 March 2018 at 06:47, Vijay Kumar Banerjee
wrote:
> It worked !
>
That's great! That's the good news then. I was using an old leon3 build
and maybe some older Qemu too and I think that's why I didn't see any
issues initially. I was hoping you could see the coverage running and the
reports
I guess I couldn't understand properly what you're suggesting ,
on the basis of what I understood ,
I have set the PATH like this
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/
lunatic/.local/bin:/home/lunatic/bin
I'm still getting the same error
-- vijay
On 17 March 2018 at 20:24, Jo
It worked !
It's great to see it running ! I have attached the result .
-- vijay
On 18 March 2018 at 02:31, Cillian O'Donnell wrote:
>
>
> On 17 March 2018 at 20:08, Vijay Kumar Banerjee
> wrote:
>
>> yes it prints hello world
>>
>
> Alright I've added an .ini for leon3-qemu to the current rte
On 17 March 2018 at 20:08, Vijay Kumar Banerjee
wrote:
> yes it prints hello world
>
Alright I've added an .ini for leon3-qemu to the current rtems-tools. Pull
this branch
https://github.com/cillianodonnell/rtems-tools/tree/ini-update
and try
$HOME/development/rtems/test/rtems-tools/tester/rt
If you run just one test by itself without rtems-test
qemu-system-sparc -no-reboot -monitor null -serial stdio -nographic -M
leon3_generic -kernel
$HOME/development/rtems/leon3/sparc-rtems5/c/leon3/testsuites/samples/hello/hello.exe
Does the hello world print out?
On 17 March 2018 at 14:46, Vija
My guess on the build error is that the automake version used by RTEMS is
very old and may not produce output for --help that help2man can parse.
Try building qemu from the RSB without the RTEMS tools in your PATH.
If Couverture has been updated to a recent enough version of the upstream
qemu, th
I built it manually
the environment variable PATH looks like this
/home/lunatic/qemu/install/bin:/home/lunatic/development/rtems/5/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/lunatic/.local/bin:/home/lunatic/bin
I tried to run rtems-test again without --coverage , it gives the sam
Vijay,
On Fri, Mar 16, 2018 at 10:59 AM, Vijay Kumar Banerjee
wrote:
> building couverture-qemu from rtems-source-builder (
> https://github.com/cillianodonnell/rtems-source-builder/tree/couverture-build
> )
> gives error building auromake-1.12.6-x86_64-linux-gnu-1 .
>
> I have attached the error
Yes this is something more than my build, I'll need someone a bit more
expert in the RSB to step in there. In the meantime, lets just build
couverture-qemu manually so we can see is everything else working.
git clone https://github.com/AdaCore/qemu
cd qemu
./configure --target-list=sparc-softmmu
the same error comes when I try to build qemu from the
RTEMS/rtems-source-builder as well
is the issue coming from my system ? I'm using fedora 27 64bit
On 17 Mar 2018 12:39 a.m., "Vijay Kumar Banerjee"
wrote:
> yes , the same thing happens
>
> On 17 Mar 2018 12:13 a.m., "Cillian O'Donnell"
>
yes , the same thing happens
On 17 Mar 2018 12:13 a.m., "Cillian O'Donnell"
wrote:
> If you build regular qemu with the RSB, does the same thing happen?
>
> Try
>
> ../source-builder/sb-set-builder --log=qemu_log.txt
> --prefix=$HOME/development/5 devel/qemu
>
>
> On 16 March 2018 at 16:48, Vija
If you build regular qemu with the RSB, does the same thing happen?
Try
../source-builder/sb-set-builder --log=qemu_log.txt
--prefix=$HOME/development/5 devel/qemu
On 16 March 2018 at 16:48, Vijay Kumar Banerjee
wrote:
> still the same error
>
> -- vijay
>
> On 16 March 2018 at 21:39, Cillian
still the same error
-- vijay
On 16 March 2018 at 21:39, Cillian O'Donnell wrote:
> Just checked and the build was failing because one of the patches needed
> its hash to be updated to sha256. Just pushed that change. The build
> finishes successfully on my end. Pull that change into couverture
Just checked and the build was failing because one of the patches needed
its hash to be updated to sha256. Just pushed that change. The build
finishes successfully on my end. Pull that change into couverture-build
branch and try it again. I'm not seeing any automake stuff here, so just
check that a
building couverture-qemu from rtems-source-builder (
https://github.com/cillianodonnell/rtems-source-builder/tree/couverture-build
)
gives error building auromake-1.12.6-x86_64-linux-gnu-1 .
I have attached the error report .
-- vijay
On 15 March 2018 at 19:17, Cillian O'Donnell wrote:
>
>
> O
On 15 March 2018 at 12:26, Vijay Kumar Banerjee
wrote:
> It runs with a bunch of errors . I have attached the log file
>
Ok, I'm guessing you didn't set up Couverture-Qemu (special version of qemu
designed for generating extra trace data for coverage analysis). That's
what those errors are about
It runs with a bunch of errors . I have attached the log file
-- vijay
On 15 March 2018 at 16:58, Cillian O'Donnell wrote:
> Looks good. If you run the samples without coverage is everything ok?
>
> So removing --coverage and tacking on /samples
>
> $HOME/development/rtems-tools/tester/rtems-t
Looks good. If you run the samples without coverage is everything ok?
So removing --coverage and tacking on /samples
$HOME/development/rtems-tools/tester/rtems-test --rtems-bsp=leon3-qemu
--log=log-leon3.log --rtems-tools=$HOME/development/rtems/5
--rtems-builddir=$HOME/development/rtems/kernel/l
I have attached the output of the ls of that directory
-- vijay
On 15 March 2018 at 15:52, Cillian O'Donnell wrote:
>
>
> On 15 March 2018 at 03:58, Vijay Kumar Banerjee
> wrote:
>
>>
>> hello ,
>>
>> as told by Joel , I started this thread to further discuss the coverage
>> analysis toolset .
On 15 March 2018 at 03:58, Vijay Kumar Banerjee
wrote:
>
> hello ,
>
> as told by Joel , I started this thread to further discuss the coverage
> analysis toolset .
>
> Current status is , I'm trying to builld and run rtems-test from the
> coverage-merge branch of the previous GSoC student Cillian
hello ,
as told by Joel , I started this thread to further discuss the coverage
analysis toolset .
Current status is , I'm trying to builld and run rtems-test from the
coverage-merge branch of the previous GSoC student Cillian .
https://github.com/cillianodonnell/rtems-tools/tree/coverage-merge
37 matches
Mail list logo
