Currently Cppcheck is being executed without any jobs specified meaning that everything is being done within a single thread. So in case something causes the application to terminate prematurely you will get a notification bubble after the failed execution.
If jobs were used the analysis would spawn a separate process (Linux) or thread (Windows - implementing process is being tracked in https://trac.cppcheck.net/ticket/12464) for the analysis. In case of using a process it would not cause the application to exit but produce a cppcheckError instead.
This will make it easier to distinguish execution failures (bad configuration) from analysis failures (bug in Cppcheck). We might also be able to display more details about the failures might it easier to collect the information necessary to report issues.
Currently Cppcheck is being executed without any jobs specified meaning that everything is being done within a single thread. So in case something causes the application to terminate prematurely you will get a notification bubble after the failed execution.
If jobs were used the analysis would spawn a separate process (Linux) or thread (Windows - implementing process is being tracked in https://trac.cppcheck.net/ticket/12464) for the analysis. In case of using a process it would not cause the application to exit but produce a
cppcheckErrorinstead.This will make it easier to distinguish execution failures (bad configuration) from analysis failures (bug in Cppcheck). We might also be able to display more details about the failures might it easier to collect the information necessary to report issues.