Version control breakpoints and tracepoints

Version control breakpoint and tracepoint insertion allows you to quickly record the state of the parts of the target program that were last modified in a particular revision. The resulting tracepoint output can be viewed in the Tracepoint Output tab or the Logbook tab, and can be exported or saved as part of a logbook or offline log.

Version control tracepoints can be inserted either in graphical interactive mode or in offline mode via a command-line argument.

In interactive mode, enable View ‣ Version Control Information. The annotation column is displayed in the Source Code viewer for files that are tracked by a supported version control system.

To find all the source files, detect the variables on the lines modified in the revision, and insert tracepoints (pending if necessary), right-click a line last modified by the revision of interest and choose Trace variables at this revision.

A progress dialog may be displayed for lengthy tasks.

You can double-click on the tracepoints and tracepoint output in the Tracepoints, Tracepoint Output, and Logbook tabs during a session to jump to the corresponding line of code in the Source Code viewer.

In offline mode, supply the additional argument --trace-changes to apply the same process as in interactive mode using the current revision of the repository.

By default, version control tracepoints are removed after 20 hits. To change this hit limit set the environment variable FORGE_VCS_TRACEPOINT_HIT_LIMIT to an integer greater than or equal to 0. To configure version control tracepoints to have no hit limit set this to 0.

See also Version control information.