Warning: You're looking at a styleless page because your browser is ignoring CSS styles. You're probably using a very old browser, or you disabled CSS support by purpose. We suggest you to download a modern browser such as Firefox or Internet Explorer.

Starting the debug session

There are three methods of starting a debug session -- from within the IDE, from the browser, and using the Just In Time feature.

From the IDE

Run (F9):

Choosing Run from the Debug menu, or clicking the Run icon on the Debug Toolbar will begin a debug session and execute the script until the first breakpoint or error. The selection of the script being executed and with what url it will be requested is defined in the settings dialog.

Run with Parameters (Shift+F9):

Choosing Run with Parameters from the Debug menu, or clicking the Run with Parameters icon on the Debug Toolbar will begin a debug session as above. In addition, it will populate the $_GET superglobal array with the parameters you specify.

Step Into (F7) and Step Over (F8):

Starting a session with Step Into or Step Over will start the session as would Run , but will pause the execution at the first line of the script, allowing you to step through the code from the beginning.

Run to Cursor

Starting a session with Run to Cursor will start the session as would Run , but will pause the execution at the line containing the caret in the active document. The execution might be paused before this line if there's a breakpoint or an error, or might not pause at all if this line is never executed.

From the browser

Make sure that your server configuration is correctly set even when starting a session from the browser, otherwise PHPEdit won't find the files being debugged, and will need to request a read only copy of them to the debugger to show you the source.

Starting a session from the browser is done by browsing to the wanted url, and adding a parameter that will instruct the debugger to start a debug session with PHPEdit. This is done differently is you are using DBG or Xdebug.

Just In Time (JIT) with DBG

For JIT to work, it must be configured correctly in php.ini. It is recommended that the HTTP Mode be the active tab in the Debugger Settings dialog. When HTTP is the active mode, files opened by PHPEdit will be the local copies of the scripts in the path set up in the Debugger Settings dialog. If a debug session is started by JIT while the debugger is in Local CGI mode, read-only copies of the remote files will be opened by PHPEdit. See the Debugger: Configuration section of the documentation for configuration instructions.

With Just In Time debugging, an error in a script will cause dbg to try to establish a session with dbgListener. This could cause potential security issues, as dbg is capable of output the entire script to a dbgListner on a foreign machine. For this reason, it is recommended to only use dbg on development servers in a trusted environment.

DebugBreak()

DebugBreak() generates an error to trigger JIT. Using DebugBreak() is not as convenient as setting breakpoints in the IDE, but it may be useful for scripts that will be debugged by multiple users who wish to start debugging from a common point.

Up Next
Home Using Breakpoints