Documentation | user: Update Tracing - Event Recording (!80)

[Chris Johns (@chris)]

Chris Johns started a new discussion on user/tracing/eventrecording.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/80#note_114814

 >  
 > -Recorded events can be sent to a host computer with a record server started by
 > -:c:func:`rtems_record_start_server` via a TCP connection.
 > +The event records produced by the application on the target system need to be
 > +transferred to a development host for analysis.  For a running application on
 > +the target system, this can be done through a TCP stream provided by the record
 > +server.  When the application on target system terminates, the latest event
 > +records can be dumped to the console device.  Custom record transfers can be
 > +done by using the :c:func:`rtems_record_dump` or :c:func:`rtems_record_fetch`
 > +functions.
 > +
 > +Get the Event Records Through a TCP Stream
 > +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 > +
 > +Recorded events can be sent to a host computer through a TCP stream provided by
 > +the record server running on the target system.  The record server is started

Should you mention the tool is built and installed when the RSB builds your tool chain?

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/80#note_114814
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20241113/21bb0f1a/attachment.htm>