GSoC Project | Basic support for Trace Compass

[Ravindra Kumar Meena]

>
> > 0 RTEMS_RECORDING_EVENT: { cpu_id = 4 }, { ns = 954631069457, events = (
> > "RTEMS_RECORD_THREAD_STACK_CURRENT" : container = 209 ), data =
> > 134621454958589 }
> > 0 RTEMS_RECORDING_EVENT: { cpu_id = 18 }, { ns = 955492534605, events =
> > ( "RTEMS_RECORD_THREAD_SWITCH_OUT" : container = 216 ), data =
> > 720857707413798909 }
> > 0 RTEMS_RECORDING_EVENT: { cpu_id = 19 }, { ns = 955499514125, events =
> > ( "RTEMS_RECORD_THREAD_SWITCH_IN" : container = 215 ), data =
> > 648799898627506173 }
>
> Is this the complete output? Do you see errors or warnings in the
> babeltrace output?
>
 No, this is not a complete output.
Yes, there is a warning about enum value. The babeltrace is reading some
enum values and some it is not reading.

There is error too:

[error] Unexpected end of packet. Either the trace data stream is corrupted
or metadata description does not match data layout.
[error] Reading event failed.
Error printing trace.

This might be happening because the last packet is not fully received in
the raw data file you pushed on my workplace.



-- 
*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/20190711/55d48efa/attachment-0002.html>