Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

always run analysis with jobs #104

Open
firewave opened this issue Jan 3, 2025 · 0 comments
Open

always run analysis with jobs #104

firewave opened this issue Jan 3, 2025 · 0 comments

Comments

@firewave
Copy link
Collaborator

firewave commented Jan 3, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant