Fix move semantics on KCursorSaver

Just moving a pointer doesn't do what we want, and is actually dangerous. The unit test would even have noticed that, if it's logic hadn't been flipped in the last step.

Found by LSAN.

Merge request reports

Loading