Re: [GSOC - Tracing] Status Update

>I am not sure you can do this without providing your own babeltrace source component in a separate plugin to what is already available. If the trace is not converted to a useful CTF format. Yes. The blog post is merely to demonstrate how to use babeltrace. We will not be dealing with text trace i

Re: [GSOC - Tracing] Status Update

On Tue, 2018-07-03 at 07:50 +0530, Vidushi Vashishth wrote: > > 3. Clearly document your modifications in separate commit messages. > > > 4. Add a Makefile to build it automatically. > > I will push commits to a fork of the rtems. Have given a link to the > repository in the readme.md of the Trac

[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 Wed, Jul 4, 2018, 1:46 PM Vijay Kumar Banerjee wrote: > On 4 July 2018 at 22:37, Joel Sherrill wrote: > >> >> >> On Wed, Jul 4, 2018, 3:06 AM Chris Johns wrote: >> >>> >>> >>> On 4/7/18 5:55 pm, Vijay Kumar Banerjee wrote: >>> > On 4 July 2018 at 13:09, Chris Johns >> >

Re: Gcov support in Covoar

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

Re: Gcov support in Covoar

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

Re: [GSoC - x86_64] Current state, next steps, and minimal mergable BSP

Hi! Quick question - when I squash and submit the patches to devel, do 2 commits make sense? 1. Initial BSP that can build completely and get to the user's Init task 2. NS16550 console driver that lets printf/printk work Another question - my code has a bunch of XXX comments in it - are we okay t

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 > > wrote: > > > > On 4/7/18 5:38 pm, Chris Johns wrote: > > > On 4/7/18 4:52 pm, Vijay Kumar Banerjee wrote: > > >> > >

Re: Gcov support in Covoar

On 4/7/18 5:55 pm, Vijay Kumar Banerjee wrote: > 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 sup

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. > >> > >> Current status is that the code in it (like in GcovData.cc) remai

Re: Gcov support in Covoar

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

Re: Gcov support in Covoar

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