...
Now, you can either just start up your chosen module in this xterm to see more output messages from it, or else you can start the debugger with it. Generally, the command-line arguments -nofork and -debug 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. Note that you may have to kill the existing instance of the module if it has already been run during this Metview session - use Metview's Process Monitor for this.
Example - debugging getting more output from the Observation Filter:
| Code Block | ||
|---|---|---|
| ||
./ObsFilter -nofork -debug |
...