If the setConfigCallback ros service is called before the node if fully initialized, there is a risk of a crash while trying to publish on the updatepub publisher.
The reason is because the publisher is created after the rosservice is advertized. reversing this order is enough to address the crash.
If the setConfigCallback ros service is called before the node if fully initialized, there is a risk of a crash while trying to publish on the updatepub publisher. The reason is because the publisher is created after the rosservice is advertized. reversing this order is enough to address the crash.