Op maandag 13 januari 2014 schreef Matthias Goldhoorn
(matthias [dot] goldhoorn [..] ...):
> 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.
Largely untested and widely unused.... Other than that, i would expect
cases of lockups sooner than cases of crashes. Don't set the activity
of the slaves in this case... Only of the master.
Peter
>
>
>
> 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 [..] ...
>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
>
>
>
>
>
> --
> Dipl.-Inf. Matthias Goldhoorn
> Space and Underwater Robotic
>
> Universität Bremen
> FB 3 - Mathematik und Informatik
> AG Robotik
> Robert-Hooke-Straße 5
> 28359 Bremen, Germany
>
> Tel.: +49 421 178 45-4193
> Zentrale: +49 421 178 45-6550
> Fax: +49 421 178 45-4150
> E-Mail: matthias [dot] goldhoorn [..] ...
>
> Weitere Informationen: http://www.informatik.uni-bremen.de/robotik