Org/Eclipse/PHP/Internal/debug/CORE/preferences/phpprojectpreferences

I encountered a very depressing thing today. I had a good time installing Zend debug in the morning, but I don't know what the problem occurred in the afternoon. The error prompt always pops up, which is inexplicable, this seriously affects productivity.

For example, org/Eclipse/PHP/Internal/debug/CORE/preferences/phpprojectpreferences, or org. Eclipse. Debug. Core. debugexception: errors related to debugging are always detected.

What content was set in the morning that caused the afternoon issue and then searched many places including Zend's official forum, http://forums.zend.com/viewtopic.php? F = 59 & t = 69053,

Similar to this:

Error creation extension for extension-point org. Eclipse. php. Internal. Debug. daemon. Communication
Plug-in COM. Zend. php. Debug. Core was unable to load class com. Zend. php. Debug. Core. Communication. advanceddebuggercommunicationdaemon.
An error occurred while automatically activating bundle org. Eclipse. php. Debug. Core (292 ).

Very vomiting blood. I re-installed Zs and deleted c: \ User \. zendstudio \ and other following content, re-installed a new version, still has a similar problem, where is the problem?

Through some similar posts:

Http://blog.csdn.net/yangfeitarena/article/details/4323778

Considering the possible Java version, the Zs I downloaded inherits the Java environment and seems to be 1.6, while the version I installed on my local machine is 1.7, and the system always prompts me to view the log error log.

I don't know where the error log is. Development hits the ceiling, and the efficiency decreases rapidly.

After careful observation, it is impossible to re-use the software.There must be something wrong with the software.I guess there may be a file bug in the directory where the file is located. And I suddenly found that if I

No error was found when switching to a workspace. Understand the reason.

Solution:

(1) Delete All Zs-related files in the current directory, so that I can find the E: \. Metadata \. Log File. At this time, my root directory is on the E disk.

(2) Reconstruction Project

The general method is as follows:

【Solution] The Zend debug environment has been set up locally, which is very convenient to debug. The key is to be able to track the entire process when accessing the new framework, this understanding of the framework will bring great convenience. So whether we can build Zend on our cloud
What about remote debugging of DEBUG? After searching, I found some solutions. After building and testing this morning, it works!
The method is as follows. I hope to help some colleagues.

 

Preparations: Zend studio 9.0.2 (use the latest version). You can find me or download the latest version from the Zend official website and crack it. For details, refer to my blog: Workshop.
Zend debug is recommended. In addition, you can download the FF plug-in zendstudio toolbar 2.6, as shown below:

 

 

This plug-in can easily start Zs debugging, page performance testing, and other functions. DownloadZendDebugger-v5.2-linux-glibc23-i386.tar.gz (see attachment), this is the Linux version, the specific operation method:

 

(1) ExtractZendDebugger-v5.2-linux-glibc23-i386.tar.gz to any directory, decompress:

 

(2) Check the PHP version of your server. For example, if the current cloud version is 5.2.14, copy the 5_2_x_comp file to the PHP template installation directory,

You can use phpinfo () to view the extension_dir Directory, which is the template installation directory. Open PHP. ini and enter the following at the end of the file:

 

Zend_extension =. So directory, full path, or CP to extension_dir directory, directly write zend_extension = zenddebugger. So

Zend_debugger.allow_hosts = is the IP address of the allowed client. Here, we enter the Intranet IP address. For example, if my IP address is 10.8.6.28, my Shenzhen colleague can write my own intranet IP address,

(If a colleague from Shenzhen needs to use this debugging function, you can add your own IP address here for testing)

Zend_debugger.expose_remotely = always

 

(3) restart the server. Restart the server elegantly by using/usr/local/apache2/bin/apachectl-K graceful and run phpinfo (), which indicates that server debugging is supported.

 

(4) the configuration of ZS is more important here. I am using this method to make it clearer. Here is the list of all servers of PHP servers. You can add them on your own.

Enter the server name and the corresponding URL. You can directly use the IP address or the domain name. You can use the domain name method and DNS resolution. You can add it to tunnel.

IP address, or add the virtual address 10.6.224.192 cloud.ied.com to the system's hosts, and then run-> debug In the Zs Toolbar
As-> PHP Web Application

Fill in the desired URL for remote debugging and start

 

(5) This is the key principle of remote debugging. Because remote debugging uses a specific interface to communicate with a remote server using local Zs, the display of debugging information must be displayed on the local machine,

So hereA code template for remote debugging must be available locally, and must be consistent with that for remote debugging.If there is any inconsistency, the debugging will produce an error, although the local machine is theoretically correct, in fact

Local Code is only a reference of remote code. This is especially evident when using PHP's require, include, and other methods. You must use the correct remote path. Otherwise

During code execution, errors such as the file does not exist may affect normal debugging.

 

Local debugging is easier. The method is similar to the above. Just imagine that the local server is a remote server. If you have any questions, feel free to discuss them with me and hope to help you. Thank you!

 

 

 

 

 

(Once you see this interface, congratulations, remote debugging is successful. Good luck !)