Advanced Debugging Features

Klive’s advanced debugging features are turned on by default. They are:

• the Execution History, with lite step back and trace export;
• reverse debugging: Step Back and Forward, Reverse Step Over and Out, Reverse Continue, and Take over here;
• debug recordings (.klr files);
• code coverage and the memory heat map.

The same switch will also cover the profiling and unit-testing features as they arrive.

With the features on, the Debug menu has the reverse-stepping commands, Execution History, Export Execution History…, Code Coverage, Reset Coverage and the debug-recording commands, and the memory view has its Heat selector. The toolbars have the Step Back, Step Forward and Return to Present buttons. The keyboard shortcuts, the history commands (show-history, step-back, history-export, debug-recording-load, coverage and the rest) and the Reverse debugging and Coverage and profiling settings groups work too.

Use these steps to turn them off:

1. Start Klive
2. In the IDE window, execute this command:

set -u features.advancedDebugging 0

3. Restart Klive

While the features are off, Klive does not record the execution history or keep a reverse-debugging timeline, so a debug session costs nothing extra. The history commands, and opening a .klr file, say how to turn the features back on:

set -u features.advancedDebugging 1

You should restart Klive after changing the setting.