Re: big issues with state machine loading

S Roderick <[email protected]> Tue, 11 Feb 2014 08:41:57 -0500
Newsgroups gmane.science.robotics.orocos.devel
Message-ID <[email protected]>
On Feb 11, 2014, at 08:31 , Peter Soetens <[email protected]> wrote:

> On Tue, Feb 11, 2014 at 10:18 AM, Thierry Bultel <[email protected]> wrote:
>> Le 11/02/2014 10:01, Peter Soetens a écrit :
>> 
>> 
>> 
>> On Sat, Feb 8, 2014 at 9:30 AM, Thierry Bultel <[email protected]> wrote:
>>> 
>>> Hi all,
>>> 
>>> We are currently evaluating orocos toolchain 2.7rc3
>>> My configuration is :
>>> 
>>> - boost-1.53.0
>>> - gcc-4.7.3
>>> 
>>> The test sample is the helloworld.cpp from the tutorials; here is the
>>> state machine script:
>>> 
>>> StateMachine States {
>>> 
>>>        initial state initState
>>>        {
>>>                entry
>>>                {
>>>                }
>>> 
>>>                transition select Final
>>>        }
>>>        final state Final
>>>        {
>>>                entry
>>>                {
>>>                }
>>> 
>>> //
>>>        }
>>> }
>>> 
>>> RootMachine  States sTates
>>> 
>>> 
>>> I am testing on 2 target architectures, the first one is intel and the
>>> second, arm
>>> The bug I am mentioning here occur one the real targets, as well as with
>>> qemu user.
>>> 
>>> On intel, comments (both "//" and "/* ...*/" )in state machine are
>>> detected as errors:
>>> 
>>> Hello [R]> scripting.loadStateMachines("statemachine.osd")
>>> 6.129 [ Info   ][ScriptingService::loadStateMachine] Parsing file
>>> statemachine.osd
>>> 6.247 [ ERROR  ][ScriptingService::loadStateMachine] statemachine.osd
>>> :Parse error at line 18: Syntactic error: Exptected ending '}' at end of
>>> state ( or could not find out what this line means ).
>>> = false
> 
> I can't reproduce this. An equally likely reason is the difference in
> Boost version, since boost::spirit changes from time to time. I'm
> using Boost 1.46.
> 
> Anyhow, there was no specific unit test for this case, so we can add
> it anyway and see on which combinations it breaks. It's now present on
> rtt's master and toolchain-2.7 branches.
> 
> Peter

We've definitely seen this behaviour in the past, and learnt not to mix code and comment lines in RTT state machines, as well as being very careful where whitespace goes. But Peter may be correct re boost, as we're using v1.53+ and haven't seen it recently (we are still on RTT v1 though).

YMMV
S

-- 
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev