You might be asking yourself how a debugger can help to produce secure software?
It is always important to verify that your expectations are proofed. The best point to do so is to inspect the behaviours while developing. No matter what kind of behaviour should be watched, you can inspect nearly every part of the application with this debugger. Most of the applications have central services like database interfaces which can easily be watched by passing the query to the debug function. Measure which and how many calls are running through your functions or just verify a single given value. Keeping track of the data flow within your application will result in a better understanding and increase the security, because every value can be verified.
Finding bugs can be an obfuscating task, especially when they are hiding in applications supposed to be stable. It is always easy to install the debugger, even in existing applications. You can analyse your code step by step, needing only a web browser and access to the file system, which is given in most development environments. The debugger provides extensive information related to your trace, so that you can easily investigate your presumptions and save a lot of time.
There are several known methods to identify security issues and to avoid them, but time limitations due to commercial aspects are often conflicting with development best practice, so that developers under pressure may not see a leak when it occurs. The debugger is trying to help the developers is such situations with detailed information and a complete picture of the running script. It shows which parts of the application are involved and what information is going in and out on the server. This should help preventing security issues, before the pressure is too high.
Preventing security leaks is a never ending story, some people would say that it is impossible to write 100% secure code, but we should do our best to reach such a high security level.