Download Whole document

This will invoke 4 processors to parallel compile PAWS. More processors can be employed by
using a higher number after -j. After compilation, an executable named PAWS_CLM can be
found in $PAWS$/bin. To clean up previously built files and re-build the project, do
make clean
By default, the code is compiled as the release version (optimized). If you want to have version
of the code with source information (so that you can debug it), edit $PAWS$/MAKE/Makefile
and $PAWS$/MAKE/subdir.mk, change
ifort -O2 to
ifort -g
make clean and make all need to be done. We can debug it in various environments (e.g.
emacs+gdb, idb, ddt or totalview). However, so far the most convenient seems to be idb as the
code is mostly compiled with ifort. There are still some character array initialization statements
that are not compatible with gfortran yet (oh dear dumb gfortran!). One downside of idb
compared to emacs+gdb is that although it does show source files during debugging, we are not
looking at the actual source code but stripped source code stored in the compiled executable and
we cannot change it. Therefore in order to edit-compile-debug again we need another text editor
like emacs on the side to actually make changes.
To debug with idb, at Linux prompt, type
idb &
When idb pops up, open the correct executable and set up correct folder/arguments like below
30