Totalview® for HPC User Guide : PART IV Advanced Tools and Customization : Chapter 23 Scalability in HPC Computing Environments : dlopen Options : dlopen Event Filtering
dlopen Event Filtering
You can filter dlopen events to plant breakpoints in the dlopened libraries only when the process stops for some other reason.
When so configured, the process never stops for a dlopen event, not even "null" dlopen events. Using this option can result in significant performance gains — but note that an application may execute past the point at which you want to start debugging inside the dlopened library, so this setting may be impractical for some applications.
dlopen event filtering is controlled by the settings on two state variables, TV::dlopen_always_recalculate and TV::dlopen_recalculate_on_match. Three possible dlopen filtering modes are made possible by these variables:
Slow Mode: Reloads libraries on every dlopen event. This is the default.
Medium Mode: Reports only libraries that match defined patterns on a dlopen event.
Fast Mode: Does not stop for dlopen events. This mode provides the best performance and is recommended when scalability is important.
You can set dlopen to use the Fast mode for all invocations of TotalView by putting the following in your tvdrc file:
dset dlopen_always_recalculate==false
dset dlopen_recalculate_on_match==""
Or, you can just launch an individual instance of TotalView with these settings by entering:
totalview -no_dlopen_always_recalculate -dlopen_recalculate_on_match ""