How do I debug problems starting VisIt or opening files?
If you are having difficulty either starting VisIt and/or looking at some data files once VisIt is running, try some of the following… Add ‘-debug 5’ to the command-line to launch VisIt. This will generate debug logs for each executable component VisIt is running in the directory that VisIt was launched from. Note that VisIt runs much slower with debugging turned on. So, it is best to use it only when you need to. On Windows systems, if you launch VisIt by double clicking the shortcut icon, you will need to modify the “Target” text field of the shortcut and include ‘-debug 5’ *after* the close double quote (“) at the end of the existing string. Also, don’t forget to remove it after you have completed debugging because running with debugging turned on causes VisIt to run much slower. Alternatively, you can make a copy of the shortcut icon, naming it something like “visit_debug” and modify only the copy. VisIt supports 5 levels of debugging. So, each component will generate 5 different
