-
Notifications
You must be signed in to change notification settings - Fork 272
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
Controller sorting can cause segfaults when interfaces are created on controller configuring #1164
Labels
Comments
Hello @fmauch! Thank you for reporting the issue. I've addressed the above bug in the linked PR. I've tested it on my end and it works. Please test us and let us know. Thank you, Best Regards, |
Thank you for helping us help you help us all |
bmagyar
pushed a commit
that referenced
this issue
Nov 14, 2023
bmagyar
pushed a commit
that referenced
this issue
Nov 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
There are controllers that specify their interfaces in
on_configure
such as theforce_torque_sensor_broadcaster
. Maybe that's an error already then we can close this here and I'll make a PR on the FTS broadcaster.However that can lead to situations where when the FTS broadcaster is loaded but not yet configured and another controller is configured the controller sorting in configuring the other controller will also check the FTS broadcasterf for sorting. For this it will try to fetch all state and command interfaces which will use the
force_torque_sensor_
object which unfortunately is a nullpointer before the FTS broadcaster has been configured.To Reproduce
Steps to reproduce the behavior:
Expected behavior
First of all I would expect things not to crash. One question is whether unconfigured controllers should be used for sorting, as well (see questions below).
Screenshots
I hope the problem is clear without screenshots.
Environment (please complete the following information):
Possible solutions / workarounds
I see two possible solutions, but I am not sure which one would be preferred:
The text was updated successfully, but these errors were encountered: