Details
-
Bug
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
2.4.2
-
None
Description
Sometimes when editing my Qbs files I run into a case where Qbs just crashes.
In QtCreator this is shown as an error in the "Issues" output window and looks like this;
At this point, I don't know if the error was "my fault" for making some unreasonable demands from Qbs or if this is just a general bug in Qbs.
In any case, I am not really able to continue my work anymore before this is resolved. In this case we have 2 ways forward:
- Backtrack my recent Qbs file changes one by one to see when things start working again. Note that this requires me to restart QtCreator for every step because Qbs is not started again automatically.
- Attach a debugger to Qbs to see in more details what happens.
So what I would like to see in this case is the following:
- The errors that shows up in "issues" in QtCreator should provide some more info, like:
- The exit code returned by Qbs
- The name of the Qbs binary that exited
- Link to documentation on how to work with debugging Qbs
- QtCreator should try to restart Qbs so I don't have to restart QtCreator
Further, when I do this:
ps aux | grep qbs
The output suggests that multiple qbs instances are started:
leo 1341863 0.0 0.0 68736 16768 ? S 10:22 0:00 /home/leo/Qt/Tools/QtCreator/bin/qbs session
leo 1341864 0.0 0.0 68736 16732 ? S 10:22 0:00 /home/leo/Qt/Tools/QtCreator/bin/qbs session
leo 1341865 0.0 0.0 68736 16736 ? S 10:22 0:00 /home/leo/Qt/Tools/QtCreator/bin/qbs session
leo 1341885 0.0 0.0 68736 16728 ? S 10:22 0:00 /home/leo/Qt/Tools/QtCreator/bin/qbs session
leo 1341886 0.0 0.0 68736 16728 ? S 10:22 0:00 /home/leo/Qt/Tools/QtCreator/bin/qbs session
leo 1341887 0.0 0.0 68736 16752 ? S 10:22 0:00 /home/leo/Qt/Tools/QtCreator/bin/qbs session
leo 1341894 0.0 0.0 68736 16748 ? S 10:22 0:00 /home/leo/Qt/Tools/QtCreator/bin/qbs session
leo 1341895 0.0 0.0 68736 16716 ? S 10:22 0:00 /home/leo/Qt/Tools/QtCreator/bin/qbs session
leo 1342452 0.0 0.0 9340 2456 pts/5 S+ 10:36 0:00 grep qbs
Being able to start Qbsin a debuggable single instance would be useful.