Re: big issues with state machine loading

Le 12/02/2014 22:00, Peter Soetens a écrit :
> On Tue, Feb 11, 2014 at 9:53 PM, Thierry Bultel <[email protected]> wrote:
>> Le 11/02/2014 21:43, Peter Soetens a écrit :
>>
>>> On Tue, Feb 11, 2014 at 3:05 PM, Thierry Bultel <[email protected]> wrote:
>>>> Le 11/02/2014 14:31, Peter Soetens a écrit :
>>>>
>>>>> 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.
>>>> Peter,
>>>>
>>>> I do not quite agree. As I said, I can reproduce the bug with boost-1.35
>>>> /
>>>> orocos-1.x, too, If I upgrade from gcc-4.3.2 (from Debian )
>>>> to gcc-4.7.3 (from buildroot).
>>>> And it is not -only- related to comments, since a comment-less state
>>>> machine
>>>> crashes as well.
>>>>
>>>> Please tell me if you need more things, for instance I can provide you
>>>> with
>>>> our gcc toolchain and sysroot,
>>>> as well as qemu-arm.
>>> Thanks for clarifying ! So the compiler it is...
>>>
>>> I'll start with setting up a virtual Ubuntu raring 64bit system which
>>> has gcc 4.7.3.
>>>
>>> That should do it to reproduce it.
>>
>> If you stay with x86 architecture, it will not crash but the "comment" bug
>> will be the clue (hopefully)
> Hmm. a bunch of unit tests crash with the 4.7 and the 4.8 compiler,
> but the state machine unit test only crashes with 4.7 (Ubuntue 13.04)
> and goes fine with 4.8 (Ubuntu 13.10) both compiled in Debug mode.
>
> To summarise, Orocos 2.7 does not work on raring or saucy yet. This is
> not nice, since initial gdb and valgrind traces did not point at
> something obvious...and it is working on a bunch of other compilers
> (including Visual Studio 2010 and LLVM/clang)
>
> Peter

Thanks Peter,

Could you please point us the test results, or the way to run them 
ourselves ?
On our side, seeing what it working or not, we could maybe consider 
upgrading
to gcc-4.8, if feasible.

If it can help you in your investigation, the bug is likely not a regression
from an Orocos version to another, because it happens with our very old 
one, too.

Regards
Thierry

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