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

Optimise analysis rerun #17

Open
karoliineh opened this issue Jan 20, 2022 · 0 comments
Open

Optimise analysis rerun #17

karoliineh opened this issue Jan 20, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@karoliineh
Copy link
Member

Currently, the analysis is rerun whenever a file with a .c extension is saved in a project that contains a GobPie configuration file. This is not optimal though, because if only one file is specified in the conf file to be analysed by Goblint, the analysis should be triggered only when this file is modified/saved.

After analysing, Goblint returns the list of analysed files, which should be then monitored for triggering a new analysis (not triggering an analysis if an unrelated .c file is opened or saved). As of now, MagpieBridge only passes the list of files, that have been opened in the editor since opening the project in VSCode. For optimising, we should get a list of saved files only.

There are a few possible solutions for this issue:

  • Monitor the saved files ourselves
  • Make MagpieBridge pass the list of saved files as an argument in the analyze method

Note: the analysis should be triggered when the relevant header files or the compilation database are modified, as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant