-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash with toolchain-2.8 #23
Comments
@RoseWall can you take a look at this when you get back? |
We haven't been able to reproduce the issue, can you provide any more information? |
I can generate the error by running fallowing ops in deployer:
|
ping |
We've found a fix for this, and @RoseWall is applying it to the other cases before creating a PR. |
The #31 fix the crash but some warnings remains: |
It's beater but: .353 [ Warning][ScriptingService] Extra argument discarded for OperationCallerC. |
When build with toolchain-2.8 conman crash (segmentation fault) when switchController is called from ROS.
deployer output :
34.172 [ ERROR ][ScriptingService] You're using call() an OwnThread operation or collect() on a sent operation without setting a caller in the OperationCaller. This often causes deadlocks.
34.172 [ ERROR ][ScriptingService] Use this->engine() in a component or GlobalEngine::Instance() in a non-component function. Returning a CollectFailure.
34.172 [ ERROR ][ScriptingService] Unknown exception raised while executing an operation.
34.172 [ ERROR ][Scheme::enableBlock] in scheme: unhandled exception in sent operation.
34.172 [ Debug ][Scheme::enableBlock] in scheme: unhandled exception in sent operation.
34.172 [ ERROR ][Scheme::enableBlock] Could not enable block because the given block is NULL.
34.172 [ ERROR ][Scheme::enableBlock] Could not enable block because the given block is NULL.
[ERROR] [1426776125.366205408]: Exception thrown while processing service call: Unable to complete the operation call. The called operation has thrown an exception
34.172 [ ERROR ][Scheme::enableBlock] Could not enable block because the given block is NULL.
The text was updated successfully, but these errors were encountered: