Please enable JavaScript to view this site.

Thread Validator Help

Navigation: The User Interface > Settings > Global Settings > General

File Cache / Substitutions

Scroll Prev Top Next More


The File Cache / Substitutions tab allows you to specify the following:


set where cached information is stored and when it gets cleared

file path substitutions to handle copying builds from build machines to development or test machines


The default settings are shown below:




Caching file locations


Thread Validator keeps a cache of known locations for files for which it needed to search, improving the speed at which files can be found.


Cache Directory instructionStep type directly or Browse to find a directory for Thread Validator to cache its information



By default, the cache is only flushed when the executable changes between sessions.


Flush cache at each new session instructionStep tick to flush the cache every session


This slightly slows down relaunch of the same executable, as the cache needs rebuilding.


Flush cache when executable changes instructionStep untick to prevent the cache being flushed at all  



When not automatically flushing, you can manually flush the cache if necessary:


Flush Cache instructionStep flush the cache now


note This is only possible when no sessions are in the session manager. The button will be disabled if any sessions are loaded.



File Path Substitutions


Some software development schemes have multiple rolling builds of their software, often enabled by using substituted disk drive naming schemes.


When you download the build to your development machine for development and testing, debugging information may reference disk drives that don't exist on your machine, for example, drive X: while your machine only has C:, D:, and E: drives.


Or you may just be copying a build from a drive on a development machine to a subdirectory on a drive on your test machine.


These options let you remap the substitution so that the Thread Validator looks in the correct place for the source code.


Add instructionStep adds a row to the File Paths Substitutions table instructionStep enter the new path that will replace the old path in the New Path column instructionStep click in the Old Path column instructionStep enter the path that is being replaced


For example, you might enter c:\users\stephen\documents for the new path and f:\dev\build for the old path.


You can double click to edit drives and paths in the table, or remove items:


Remove instructionStep removes selected substitutions from the list


Alternatively, press b_del to delete selected items, and b_ctrl + b_a to select all items in the list first.



Example: Changed disk drive

Project originally located at


Project copied to


New Path


Old Path



Example: Project copied to a new location

Project originally located at


Project copied to


New Path


Old Path




Reset All - Resets all global settings, not just those on the current page.



Reset - Resets the settings on the current page.