Since https://github.com/goblint/analyzer/pull/599, the analysis can be aborted by sending the SIGINT signal to the Goblint server process. It's not entirely obvious when this should be done though. The possibilities I can think of right now are:
A button to manually abort a started analysis. Not sure whether Magpie allows us to have such a button somewhere though.
When one analysis is still running and the code is changed, thus calling for another analysis. Currently I guess the server mode inevitably blocks and waits for the first one to finish before sending the second analysis request. Instead GobPie could abort the first analysis, ignore the result and immediately start the second one.
The analysis abort feature is likely to expose some Goblint-side bugs as well, regarding its internal global state, so even if supported by GobPie, it might not initially be reliable enough to use. But it's worth trying out because otherwise nothing else will reveal those bugs either.
Since https://github.com/goblint/analyzer/pull/599, the analysis can be aborted by sending the SIGINT signal to the Goblint server process. It's not entirely obvious when this should be done though. The possibilities I can think of right now are:
The analysis abort feature is likely to expose some Goblint-side bugs as well, regarding its internal global state, so even if supported by GobPie, it might not initially be reliable enough to use. But it's worth trying out because otherwise nothing else will reveal those bugs either.