The Debugger

The UHSD debugger is not true debugger. What it does is goes thorugh some code and lets the user know when it thinks it may have found a syntax error. You can set the debugger to go through the security checker or through the add-ons of any game. In addition, you can have the debugger go through some custom code that you've written. Here's a list of things you NEED to know when using the debugger:

  1. The debugger will not tell you exactly what the error is, just where it is.
  2. It's not perfect. The debugger only checks code that gets executed. That means that if you have an else block (or something like it) that doesn't get executed, the debugger will not check for errors. To check those blocks, define a variable such that the block will get executed.
  3. When debugging the security check or add-ons, be aware that the variables that are normally defined in add.cgi will not be defined in the debugger. If you have a division anywhere in your code, be aware that the debugger will report an error on division by zero (undefined variables are taken to be zero). I've given $secure and $scored random numeric values to help cut down on division by zero errors, but the errors will still occur. I would suggest defining some variables at the top of the script (you can do that to simulate certain score submissions).
  4. The debugger executes the code that it debugs. If you have any code that may alter a file, I suggest that you either comment it out or change it during the debugging process.

Back to Index