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.
Currently, the analysis is rerun whenever a file with a
.cextension 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
.cfile 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:
analyzemethodNote: the analysis should be triggered when the relevant header files or the compilation database are modified, as well.