Describe the bug
I'm compiling my project with Jam and it seems to be taking care of unfinished child processes and unfortunately disown doesn't disassociate rc from Jam enough.
To Reproduce
It is unfortunately difficult to reproduce as I think it depends on gcc to finish running before rc is done but when rc needs to connect to a server this could be longer than gcc.
Expected behavior
Jam shouldn't complain about waif child processes. It shouldn't be aware that an rc process has been launched.
Screenshots/Backtrace
N/A
Environment (please complete the following information):
OS/Version: Ubuntu 18.04
RTags(rdm,rc): latest in master
Proposed solution
Change gcc-rtags-wrapper.sh to run setsid $rc instead of just $rc &
(Probably disown wouldn't be necessary after setsid I guess...)
The other solution might be to stop running rc in parallel.
Describe the bug I'm compiling my project with Jam and it seems to be taking care of unfinished child processes and unfortunately disown doesn't disassociate rc from Jam enough.
To Reproduce It is unfortunately difficult to reproduce as I think it depends on gcc to finish running before rc is done but when rc needs to connect to a server this could be longer than gcc.
Expected behavior Jam shouldn't complain about waif child processes. It shouldn't be aware that an rc process has been launched.
Screenshots/Backtrace N/A
Environment (please complete the following information):
Proposed solution Change gcc-rtags-wrapper.sh to run setsid $rc instead of just $rc & (Probably disown wouldn't be necessary after setsid I guess...)
The other solution might be to stop running rc in parallel.