GSoC Project | Basic Support for Trace Compass

Ravindra Kumar Meena rmeena840 at gmail.com
Tue Jun 25 07:55:08 UTC 2019


>
> > Hi Sebastian,
> >
> > I have sent the two patches. One is event stream file generation patch
> > and another one is metadata for it. Please apply the patches.
>
> Could you please check it in your rtems-tools repository.
>
Yes. I have already updated it. My rtems-tools workplace is
https://github.com/rmeena840/rtems-tools/tree/ravindra-rtems

>
> >
> > Run the following command for like 5 seconds so that it can generate
> > enough event traces.
> > ./build/misc/rtems-record -H 169.254.192.22 -p 1234 | head
>
> Please change the record client to use a file in the repository. So that
> we can test with the same data and without the need to run Qemu.
>
> >
> > you will get file named event in folder "rtems-tools". The metadata file
> > is in "misc/ctf/metadata". Please move the event stream file in it.
> >
> > Now, run "babeltrace ctf/" command. Here "ctf" is folder name containing
> > event stream file and metadata.
> >
> > Now you will be able to see that babeltrace is able to read the events.
> >
> > I have cross-checked the the values it is printing. All
> > values(ns,cpu,data) are correct accept the value of
> > events(rtems_record_event).
> >
> > I am currently figuring out why rtems_record_event is giving wrong value.
>
> Ok, good. Nice progress.
>
Thanks :) :)


-- 
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190625/2b5d09d1/attachment-0002.html>


More information about the devel mailing list