Bug when failing calls in state machine entry function

Submitted by snrkiwi on Thu, 2010-11-11 14:56

RTT v1 state machine, if I have an entry function like this

 state XXX
  	{
		entry
		{
			try YYY.start() 
    	        }

or this

	var bool	startedOk   = false;
...
 state XXX
  	{
		entry
		{
			set startedOk = true
			try YYY.start() catch { set startedOk = false }
    	        }

and I set YYY::start() to return false, then the state machine goes into error. According to the doc's this should not happen. Even just "try YYY.start()" should continue, right? See Sections 3.2.7 and 3.2.8 at

http://people.mech.kuleuven.be/~orocos/pub/stable/documentation/rtt/v1.1...

Any ideas?
S

‹ Unloading /usr/local/orocos/lib/liborocos-deployment-gnulinux.so: not a valid component library IROS 2010 paper mentioning Orocos ›
»

Bug when failing calls in state machine entry function

Submitted by peter on Thu, 2010-11-11 20:40.

On Thu, Nov 11, 2010 at 3:54 PM, Stephen Roderick <kiwi [dot] net [..] ...> wrote:
> RTT v1 state machine, if I have an entry function like this
>
> 

>  state XXX
>        {
>                entry
>                {
>                        try YYY.start()
>                }
>

>
> or this
>
> 
>        var bool        startedOk   = false;
> ...
>  state XXX
>        {
>                entry
>                {
>                        set startedOk = true
>                        try YYY.start() catch { set startedOk = false }
>                }
>

>
> and I set YYY::start() to return false, then the state machine goes into error.  According to the doc's this should not happen. Even just "try YYY.start()" should continue, right? See Sections 3.2.7 and 3.2.8 at
>
> http://people.mech.kuleuven.be/~orocos/pub/stable/documentation/rtt/v1.1...
>
> Any ideas?

It's a bug. I'll add your case to the unit tests, probably it was only
tested in program scripts and not in state machines.

Peter
--
Orocos-Users mailing list
Orocos-Users [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users

»