In order to debug Metview, you must first ensure that it has been built with debugging enabled. This involves setting the --enable-debug
flag when running the configure
script - see the Installation Guide for Metview 4.4 and below.
When debugging a Metview module, the debugger must be started from the correct environment.
xterm
' (without the quotes) in it, and saveFrom a terminal which has the correct environment as described above, you can go to Metview's executable directory:
cd $METVIEW_BIN
From here, you can start the debugger with your chosen module. Generally, the command-line argument -nofork
should be supplied. In the case of the Macro module, -serve
should also be supplied. If the module does not start, then it might be because it is already running - from a Metview desktop, choose Process Monitor from the Tools menu and stop the process. If debugging the Display Window, then the corresponding executable is called uPlot
; running this will create an empty Display Window into which you can drop icons.