If we have a mu action inside another mu action, the type checker will crash and produce an "Unknown" error in the tool.
Here is a minimal example, cut down from a SysML generated model
process Test = begin
@ mu X @ (
act1;
mu X @
(act2))
end
If you run this model in the tool, act1 will correctly produce a "not in scope" error. The next error is Unknown and no error appears regarding act2 (see figure).
The crash occurs in overture.core.typechecker.Environment line 111 where a null location is produced. It's possible that this is a parser error and locations are not being set properly for nested mu actions.
If we have a mu action inside another mu action, the type checker will crash and produce an "Unknown" error in the tool.
Here is a minimal example, cut down from a SysML generated model
If you run this model in the tool,
act1
will correctly produce a "not in scope" error. The next error isUnknown
and no error appears regarding act2 (see figure).The crash occurs in
overture.core.typechecker.Environment
line 111 where a null location is produced. It's possible that this is a parser error and locations are not being set properly for nested mu actions.