Re: big issues with state machine loading

S Roderick <[email protected]> Sun, 09 Feb 2014 07:37:50 -0500
Newsgroups gmane.science.robotics.orocos.devel
Message-ID <[email protected]>
On Feb 9, 2014, at 04:35 , 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 occurs on the real targets, as well as with qemu user emulation. 
> 
> 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               
> 
> 
> On arm, that directly leads to a SIGSEGV. I do not have a backtrace for now, unfortunately.
> 
> 
> I would like to add that the bug is also reproducible with orocos-1.1x and boost-1.35, letting me think
> that this could be due to the compiler version. Our investigations have failed to identity the cause,
> and I wanted to try with latest orocos version before posting.
> 
> Regards
> Thierry

We still use v1, and have learned not to mix comments and code on the same line. But /* ... */ and // comments work fine for us on x86.

We have also seen some odd issues with gcc 4.7, and also gcc 4.6. We have restricted ourselves to using gcc 4.4 only, and that seems to work.

HTH
S

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