Rev 15185 | Go to most recent revision | Details | Last modification | View Log | RSS feed
Rev | Author | Line No. | Line |
---|---|---|---|
15174 | bpr | 1 | To debug in an administrative module, several possibilities. |
2 | <ul><li>You can set the command $emph !debug$emphend |
||
3 | in the chosen location of the module files followed by variable names |
||
4 | that you want to get value. The program will stop there |
||
5 | if the execution passes it through and then displays the values of the variables |
||
6 | in question. |
||
7 | </li><li> |
||
8 | The number of the file lines in which the program runs are in |
||
9 | the file trace.txt of the tmp/sessions/XXXX directory where XXXX is the session number, |
||
10 | each time the program is executed from a server administrator IP and if the |
||
11 | the debug mode is enabled (it is then written $emph tmp_debug=yes$emphend in |
||
12 | log/wims.conf). |
||
13 | You can add a $emph tmp_debug_var$emphend variable to the log/wims.conf file |
||
14 | and assign to it as values the list of variables whose evolution we want to know |
||
15 | when running the program. |
||
16 | </li><li> |
||
17 | In debug mode, peripheral software error messages are displayed at the bottom of |
||
18 | the html page. |
||
19 | </li> |
||
20 | </ul> |