Problem
When the hardware communication process dies and the dynamic graph process is still alive, the dynamic graph process becomes a ghost process.
Potential solution
A possible way to improve this is to use the main process only for observing the other processes and shutting them down. This is in contrast to the current setup where the motor-process is the "main" process.
This would look something like this:
- Launch the main executeable - main process is created
- Fork the hardware process
- Fork the dynamic graph process
- Wait until the main process receives an interrupt signal or ros::is_okay becomes false or the hardware process dies.
- In this case, send the interrupt / kill signal to all still running processes
- Wait until all started processes have finished.
- Exit the main process.
Problem
When the hardware communication process dies and the dynamic graph process is still alive, the dynamic graph process becomes a ghost process.
Potential solution
A possible way to improve this is to use the main process only for observing the other processes and shutting them down. This is in contrast to the current setup where the motor-process is the "main" process.
This would look something like this: