Hi Frank, Thanks for your email I've seen that the BaseSearcher has 2 utility functions for adding and removing a state. Since I'm working on a searcher, if I don't add the states in added states() into states() it'd be like remove them isn't it?
Thanks On Mon, Oct 29, 2018, 11:57 Frank Busse <f.bu...@imperial.ac.uk> wrote: > Hi Alberto, > > > On Fri, 26 Oct 2018 13:41:45 +0100 > Alberto Barbaro <barbaro.albe...@gmail.com> wrote: > > > I'm on a searcher and I would like to remove the current state from > states. > > Should I added it to removedStates or do something else? Can I have the > > example one line code if not too much? > > to gracefully shut down a state in Executor you have to call one > of the terminate functions and afterwards call updateStates() to notify > the searchers. The resp. state is added to removedStates automatically > in terminateState() and removedStates is only used to forward the > information to the searchers. Currently there is no clean way to > terminate a state in a searcher (we discussed that internally a while > ago). What you could do is: > > - initialise your searcher with a reference to the executor or > - mark the state (or return tuple in select() etc.) and adapt the main > interpreter loop (select/delete until un-marked state found) > > The 2nd option is less error-prone. > > > Kind regards, > > Frank >
_______________________________________________ klee-dev mailing list klee-dev@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/klee-dev
