Hello,
On 28/06/18 05:48, Vidushi Vashishth wrote:
Hi!
Sorry for the delay. I had been trying to make the code run.
https://github.com/VidushiVashishth/babeltrace/tree/master/Demo
This is a demonstration of the how to use babeltrace to convert rtems
traces.
which use case does this address? What is the connection to an RTEMS
application?
Why do I need sudo to run the commands?
Using my openSUSE 42.3 babeltrace yields:
babeltrace run --component=A:source.text.dmesg
--params='no-extract-timestamp=no' --key=path --value ./rtemtrace
--component=B:sink.ctf.fs --key=path --value ./ --connect=A:B
Error parsing options.
BabelTrace Trace Viewer and Converter 1.2.4"
When I compile the babeltrace clone from you, then I get:
../install/bin/babeltrace run --component=A:source.text.dmesg
--params='no-extract-timestamp=no' --key=path --value ./rtemtrace
--component=B:sink.ctf.fs --key=path --value ./ --connect=A:B
ctf.fs sink creating trace in .//rtemtrace-1
Why do I need your babeltrace? Not being able to use a tool from a
standard distribution makes it harder to do RTEMS tracing.
From your Readme.md:
"These commands will show the generated metadata stream and a ctf trace
stream."
What can I do with a metadata stream and the CTF trace stream?
At the moment I have absolutely no idea how I can use this stuff to do
RTEMS tracing. I thought that I can trace an RTEMS application (e.g.
task switches) and then see some graphical output in a tool like Trace
Compass (http://tracecompass.org/#screenshots).
Quite frankly, I don't think that you worked 30+ hours per week on
average for this GSoC project. If you want to pass the next evaluation,
then you really have to work harder.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
