On Mon, Dec 10, 2012 at 4:00 PM, Markus Klotzbuecher
<markus [dot] klotzbuecher [..] ...> wrote:
> On Mon, Dec 10, 2012 at 03:30:37PM +0100, Herman Bruyninckx wrote:
>> On Mon, 10 Dec 2012, Markus Klotzbuecher wrote:
>>
>> >On Sun, Dec 09, 2012 at 09:55:17PM +0100, Peter Soetens wrote:
>> >>On Thu, Dec 6, 2012 at 2:21 PM, Markus Klotzbuecher
>> >><markus [dot] klotzbuecher [..] ...> wrote:
>> >>>On Thu, Dec 06, 2012 at 02:14:47PM +0100, Bert Willaert wrote:
>> >>>>Hi,
>> >>>>
>> >>>>Is it possible to get the rFSM output (state_ENTER ... state_EXIT ...) in a
>> >>>>different terminal/window? It is definitely interesting to see these messages
>> >>>>online but they make it hard to use the taskbrowser to go to components, check/
>> >>>>set properties, ...
>> >>>
>> >>>You'll need to define a new 'dbg' hook, e.g. gen_dbg2file that writes
>> >>>the messages to a file which you can run "tail -f" on. Or try
>> >>>rfsm-commander to see the fsm transitioning online.
>> >>
>> >>A more standard solution would be to log to our own log4cpp logger
>> >>infrastructure.
>> >
>> >Yes, that would be the best solution. See here for more information
>> >[1]. This raises the question of whether we should extend scripting
>> >with log4cpp support to be able to do this in hard real-time?
>>
>> And what is your personal answer to this question...?
>
> Yes, if there is sufficient interest.

Standard RTT scripting already supports hard-rt log4cpp through the
RTT::rt_string data type (depending on tlsf for memory management).
But no standard operations are added and no 'logging' Service is
present in such a component, which should be a trivial extension of
the OCL::logging::Category class though.

So one could at least test if the rt_strings works for rttlua as well,
and check with valgrind if there are any memory allocations.

There's also a 'logging/tests/setup_logging.lua' example in OCL, for
setting up, but not for using it from lua.

Peter