Subversion Repositories wimsdev

To debug in an administrative module, several possibilities.

We list here some debugging methods of an administrative module.

<ul><li>You can set the command $emph !debug$emphend

<ul><li>You can add anywhere in a module file writen in wims language

in the chosen location of the module files followed by variable names

(this excludes for instance shell files) a line starting with the

that you want to get value. The program will stop there

instance :<br/> $emph !debug The score of $$user is $$score $emphend

if the execution passes it through and then displays the values of the variables

the variable names replaced by their values. In the above example, the

in question.

$emph The score of Ted Watson is 7$emphend <br/> </li>

</li><li>

The number of the file lines in which the program runs are in

can be stored for debugging purposes in a special file named trace.txt

the file trace.txt of the tmp/sessions/XXXX directory where XXXX is the session number,

in the tmp/sessions/XXXX directory where XXXX is the session

each time the program is executed from a server administrator IP and if the

is executed from a server administrator IP and the debug mode is

the debug mode is enabled (it is then written $emph tmp_debug=yes$emphend in

enabled (it is then written $emph tmp_debug=yes$emphend in

You can add a $emph tmp_debug_var$emphend variable to the log/wims.conf file

log/wims.conf).  You can add a $emph tmp_debug_var$emphend variable to

and assign to it as values the list of variables whose evolution we want to know

the log/wims.conf file and assign to it as values the list of

In debug mode, peripheral software error messages are displayed at the bottom of

variables whose evolution you want to know when running the program.

</ul>

</li> </ul>