PHP development tool ZendStudio Xdebug tool instructions for use _ PHP Tutorial

Detailed instructions on the use of Xdebug tools under PHP development tool ZendStudio. It has been more than half a year since I learned the basic knowledge of PHP and used ZendSudio for development. during this process, I learned from each other intermittently and encountered more than N problems. learning PHP is really hard to worry about. It has been more than half a year since I learned the basics of PHP and used ZendSudio for development. during this process, I encountered many problems due to intermittent learning. learning PHP is really hard to worry about. The least worry is the computing and debugging process.

To learn programming, you must understand debugging. Otherwise, you will be confused about the running mechanism. It may be because I am not a professional engineer, I am not good at understanding, or the xdebug tool itself is complicated. as a result, I am full of surprises about Zendstudio's Debugging process.

I am using XAMPP's integrated development platform environment. The Xdebug debugging tool has been preset. you only need to modify the configuration.

My development mode is to build an XAMPP environment on a virtual machine, and then the IDE environment is on the local machine. This causes remote debugging. However, Xdebug has already provided such a solution, which is quite powerful.

At first, I was in a hurry and did not fully understand the use and configuration information of Xdebug. I was in a hurry to get my ducks on the shelves, but there was a problem in a few days. the started session was stopped at 57%. later, the breakpoint did not take effect, and it suddenly ran.

After observing Port 9000, the client started Port 9000 to listen for and receive debugging information from the server. This means that the slave server can telnet Port 9000 to the client, however, the client cannot connect to Port 9000 of the server.

Final Solution: set up the xampp environment again, reconfigure it, and then enable debugging information.

Bytes. The least worry...