Curt Zirzow has pointed out a cool article on the Box.net website about debugging your PHP applications with a combination of Vim and XDebug (on linux).

Here's how it works. You're coding away in vim. You hit F5; Vim waits for a connection from the PHP server. You refresh the PHP page you're working on. It attempts to contact Vim — connection successful. You are launched into a debugging session right inside Vim. You can step into, over, and out of statements, eval statements, get all variables in context, get and set properties, remove and set breakpoints, all on the fly. Finally, some real programming tools.

Included are the steps to set up the vim environment , set up the client debugger (DGBp) and link it all to the XDebug functionality on your remote machine.

Curt Zirzow has pointed out a cool article on the Box.net website about debugging your PHP applications with a combination of Vim and XDebug (on linux).

Here's how it works. You're coding away in vim. You hit F5; Vim waits for a connection from the PHP server. You refresh the PHP page you're working on. It attempts to contact Vim — connection successful. You are launched into a debugging session right inside Vim. You can step into, over, and out of statements, eval statements, get all variables in context, get and set properties, remove and set breakpoints, all on the fly. Finally, some real programming tools.

Included are the steps to set up the vim environment , set up the client debugger (DGBp) and link it all to the XDebug functionality on your remote machine.

Derick Rethans has posted a part two to the post from Guy Harpaz yesterday concerning the debugging protocol "shootout" that Derick began in previous posts.

Derick's latest post looks at some of the comments Guy made, including comments about Zend's choice of implementation and their suggestions as to why you should choose the Zend Studio's debugging protocol over DBGp.

Other topics that Derick comments on in the post include the mentions of bugs in DBGp's Proxy mechanism, proxy requirements, and the functionality of Zend's "specific protocol for PHP" in handling headers/body informzation.

Derick Rethans has posted a part two to the post from Guy Harpaz yesterday concerning the debugging protocol "shootout" that Derick began in previous posts.

Derick's latest post looks at some of the comments Guy made, including comments about Zend's choice of implementation and their suggestions as to why you should choose the Zend Studio's debugging protocol over DBGp.

Other topics that Derick comments on in the post include the mentions of bugs in DBGp's Proxy mechanism, proxy requirements, and the functionality of Zend's "specific protocol for PHP" in handling headers/body informzation.