Search Path Variables That You Can Set
TotalView uses the following variables when it searches for source, object, shared library, and program files:
• SOURCE_SEARCH_PATH
• OBJECT_SEARCH_PATH
• SHARED_LIBRARY_SEARCH_PATH
• EXECUTABLE_SEARCH_PATH
Each contains a list of paths, with paths separated by a colon.
Related to these variables are four additional similarly named variables. Each contains pairs of regular expressions and replacement strings—these replacements are called mappings—separated by colons. TotalView applies these mappings to the search paths before it looks for source, object, shared library, and program files:
• SOURCE_SEARCH_MAPPINGS
• OBJECT_SEARCH_MAPPINGS
• SHARED_LIBRARY_SEARCH_MAPPINGS
• EXECUTABLE_SEARCH_MAPPINGS
The syntax for mapping strings is:
+regular_exp+=+replacement+ :+regular_exp+=+replacement+
This example shows two pairs, each delimited by a colon (“:”). Each element within a pair is delimited by any character except a colon. The first character you enter is the delimiter. This example uses a “+“ as a delimiter. (Traditionally, forward slashes are used as delimiters. This is not a good idea as a forward slash is also used to separate components of a pathname. For example, /home/my_dir contains forward slashes.)
When you enter information, be careful when you include special characters. When you do, these characters must follow standard Tcl rules and conventions. For example:
dset EXECUTABLE_SEARCH_MAPPINGS
{+^/nfs/compiled/u2/(.*)$+ = +/nfs/host/u2/\1+ }
This expression tells TotalView that if it finds a directory named /nfs/compiled/u2/project/src1 in the expanded search path, it will become
/nfs/host/u2/project/src1 after applying this mapping.
related topics