Profiling and debugging

The macros TIME, TRACE and AGAT provided by SALLI remain available in $\Sigma{}^{{\rm it}}$. In addition, $\Sigma{}^{{\rm it}}$ also comes with a debug version, which makes many assertions about the arguments of the functions called as well as their results. While those assertions slow down the code considerably they tend to be quite useful when chasing bugs since the release version of $\Sigma{}^{{\rm it}}$ does not make validity checks to most of its inputs. The debug version of $\Sigma{}^{{\rm it}}$ must be used jointly with the debug version of SALLI. To use them, just set your SALLIROOT and SUMITROOT variables to the salli/debug and sumit/debug directories rather than salli, and make sure that your LIBPATH variable contains salli/debug/lib and sumit/debug/lib rather than salli/lib or sumit/lib. In addition, you must compile your application with the -q1 option rather than -q2 or -q3 in order to turn on your own assertions as well as to prevent inlining. You must also use the -dDEBUG option, which causes Integer to be defined to be AldorInteger, allowing you to use the debug version of $\Sigma{}^{{\rm it}}$ inside the interactive loop of the compiler. Do not forget to type #include "sallinterp" following #include "sumit" when inside the interactive loop.