GSoC Project | Basic support for Trace Compass

Sebastian Huber sebastian.huber at embedded-brains.de
Thu Jul 11 06:13:59 UTC 2019


On 11/07/2019 07:52, Ravindra Kumar Meena wrote:
>      > 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.

You should definitely pay more attention to warnings. Please include 
them in your emails. When you hide things we cannot help you.

The event streams you produced simply do not correspond to your 
metadata. You should spend more time to verify your results. You are to 
quick to accept things as correct.

I fixed the issue in this commit:

https://github.com/rmeena840/rtems-tools/commit/02d796748352ee675d3e4b481056022cc5fb5252

We started with this task on June 28th.

https://lists.rtems.org/pipermail/devel/2019-June/026414.html

It took 8 work days to get a more or less working solution. This is too 
much time. I can accept that you have some difficulties with writing 
programs in C, but for the CTF part you definitely should work harder to 
understand how it work.

> 
> 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.

I am pretty sure this is error is caused by something else. How many 
files do you open, how many do you close properly?

-- 
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.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.


More information about the devel mailing list