GSOC'18 project description

[Chris Johns]

On 01/05/2018 02:09, Gedare Bloom wrote:
> This is a good and important question. I think there should be a
> section in this User Manual under Host Tools for the Babeltrace/Debug
> tools that use the CTF output. There will also likely need to be
> additions to the Classic API guide for "Configuring a System" and
> improvements to description of the Capture Engine, which I'm currently
> having trouble finding.

I do not think there is anything in the user manuals. There are:

https://devel.rtems.org/wiki/TBR/UserManual/Capture_Engine

and:

https://devel.rtems.org/wiki/Developer/Tracing
https://devel.rtems.org/wiki/Developer/Tracing/Trace_Buffering
https://devel.rtems.org/wiki/Developer/Tracing/Trace_Linker

The last link details a key requirement...

  A key requirement of the trace process in RTEMS is to take
  existing code in a compiled format (ELF) and instrument it
  without rebuilding that code from source and without annotating
  that source with trace code. The code being trace may be from a
  3rd party or already certified or in the process of being
  certified and the trace testing is part of that process.

We have avoided building specialised kernel images to trace. This comes from
users like ESA.

Chris