const char **ompd_dll_locations;
SummaryThe ompd_dll_locations global variable indicates the location of OMPD libraries that are compatible with the OpenMP implementation.
DescriptionAn OpenMP runtime may have more than one OMPD library. The tool must be able to locate the right library to use for the OpenMP program that it is examining. The OpenMP runtime system must provide a public variable ompd_dll_locations, which is an argv-style vector of filename string pointers that provides the name(s) of any compatible OMPD library. This variable must have C linkage. The tool uses the name of the variable verbatim and, in particular, does not apply any name mangling before performing the look up. The programming model or architecture of the tool and, thus, that of OMPD does not have to match that of the OpenMP program that is being examined. The tool must interpret the contents of ompd_dll_locations to find a suitable OMPD that matches its own architectural characteristics. On platforms that support different programming models (for example, 32-bit vs 64-bit), OpenMP implementations are encouraged to provide OMPD libraries for all models, and that can handle OpenMP programs of any model. Thus, for example, a 32-bit debugger that uses OMPD should be able to debug a 64-bit OpenMP program by loading a 32-bit OMPD implementation that can manage a 64-bit OpenMP runtime.
ompd_dll_locations points to a NULL-terminated vector of zero or more NULL-terminated pathname strings that do not have any filename conventions. This vector must be fully initialized before ompd_dll_locations is set to a non-null value, such that if a tool, such as a debugger, stops execution of the OpenMP program at any point at which ompd_dll_locations is non-null, then the vector of strings to which it points is valid and complete.