rqt plugin crash when publisher node stops
I have made a rqt plugin that subscribes to a node. When that node stops, rqt crashes. I want detect that the node has stopped through some kind of exception handling to prevent rqt from crashing. I have done the same for a rqt plugin that calls a service with rospy.ServiceException and gotten the desired behavior. Does anyone have a suggestion to a solution for this problem?
How does the rqt plugin crash? What is the error?
There is no error. rqt just closes.
There is no output at all in the console? What about a log file under
~/.ros/log? If there is nothing in either of those, you will need to run rqt in gdb and get a backtrace you can post here.Hi, sorry for the late reply. I tried to run it again now and the console gives the following output: [1] 5128 segmentation fault (core dumped) rqt. I also found the log files, but not sure what I'm looking for...
If you post the log files then we can look for you.
A segmentation fault means that there is probably a bug in your code where you are trying to access invalid memory. You should post your code as well.
I am not allowed to upload my log files due to not enough points. I get error: [Errno 104] Connection reset by peer in the rqt gui node. Below is a link to my repository. The repository subscribes to a few nodes in rov-control under vortexntnu. https://github.com/vortexntnu/rov-gui