Status of SlaveActivity support?

Hi,

I'm on toolchain 2.5 and using a scheduler that relies on those
SlaveActivities (https://github.com/kmarkus/fbsched).

It's working perfectly in my case.

2014/1/10 Matthias Goldhoorn <goldh>

> I started to play around with sharing execution engines for slave
> activities. Concrete I using for all slave tasks the execution engine from
> the master. Unfortunately I got some segfaults or the tasks does not get
> triggered. Sylvain mentioned this might be deprecated functionality . So I
> would ask if this is still supported by RTT before I start debugging into
> it.
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>

Status of SlaveActivity support?

I'm sorry the Subject was misleading, maybe i was already too late this day.

my question was regarding the status of the "Sharing Execution Engines",
not the SlaveActivity in general.
The SlaveActivity is working fine (besides the pachtes i send to the dev
ML). My problem is sharing the execution engine from the master for the
slaves.

Matthias

On 12.01.2014 17:58, Willy Lambert wrote:
> Hi,
>
> I'm on toolchain 2.5 and using a scheduler that relies on those
> SlaveActivities (https://github.com/kmarkus/fbsched).
>
> It's working perfectly in my case.
>
>
> 2014/1/10 Matthias Goldhoorn <goldh >
> I started to play around with sharing execution engines for slave
> activities. Concrete I using for all slave tasks the execution
> engine from the master. Unfortunately I got some segfaults or the
> tasks does not get triggered. Sylvain mentioned this might be
> deprecated functionality . So I would ask if this is still
> supported by RTT before I start debugging into it.
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> <mailto:Orocos-Users [..] ...>
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
>
>
>