Zend 调试器在索引页后终止
我有一个使用 Zend Framework 运行的网站，并且正在尝试设置 Zend Debugger。 Zend 调试器已安装，并且它可以在教程 PHP 页面中正常工作，但是当我尝试使用我的应用程序进行调试时，它将适用于索引页面，但调试器将终止。
我正在运行 Apache2.2 和 PHP 5.3。
我有一个虚拟主机设置 - dev.mysite.com 指向index.php，所以我没有使用 http://localhost/我的网站
I have a website running using Zend Framework and am trying to setup Zend Debugger. Zend Debugger is installed and it works correctly with the tutorial PHP pages however when I try debugging with my app, it will work for the index page but then the debugger will terminate.
I am running Apache2.2 with PHP 5.3.
I have a virtual host setup - dev.mysite.com that points to index.php so I'm not using http://localhost/mysite
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
Zend 论坛中有一个关于设置 Zend 调试器< /a>.
如果本文中的信息没有帮助，请尝试更具体地说明您的设置。我的猜测是您的 ZF 项目中缺少
dummy.php，但是问题中确实没有足够的有关您的设置的信息来确定。There is a sticky note in the Zend Forum dealing with Setting Up Zend Debugger.
If the information in the article won't help, try to be more specific about your setup. My guess is you're missing
dummy.phpin your ZF project, but there is really not enough information about your setup in the question to say for sure.我刚刚在 Ubuntu 上安装了 Apache 2，结果发现 mod_rewrite 默认情况下未启用。我需要执行“sudo a2enmod rewrite”，现在调试器似乎可以正常工作。
I had just installed Apache 2 on Ubuntu and it turns out that mod_rewrite is not enabled by default. I needed to do "sudo a2enmod rewrite" and now the debugger seems to work properly.
我也遇到了一些问题，我的问题归结为一个陷阱和一个不太明显的问题，
即 Eclipse 浏览器设置被设置为使用内部浏览，“默认系统浏览器”恰好是 chrome。这意味着它将启动 chrome 但连接到内部浏览器。当配置为外部浏览器和明确的 chrome 而不是默认系统浏览器时，它开始工作。窗口|偏好 | Web 浏览器设置的常规
第二个问题是关于符号链接的。我使用符号链接将存储库中的源链接到框架层次结构中。这意味着 Eclipse 项目资源管理器看到一个文件（符号路径），而调试器看到另一个文件（存储库内的“rela”路径）。因此，调试器看不到在文件的 php 资源管理器版本中设置的断点。我通过检查框架目录旁边的存储库解决了这个问题，像以前一样将我的存储库文件夹符号链接到框架中，但在符号链接上使用 eclipse“从构建路径中排除”，以便 php 资源管理器和调试器都看到文件的真实路径
I had some issues with this as well, my issues came down to one gotcha and one less obvious thing
the gotcha was the eclipse browser setting was set to use internal browse, 'default system browser' which happened to be chrome. This meant that it would launch chrome but connect to the internal browser. that started working when configered for external browser and explicitly chrome rather than default system browser. Window | Preferences | General for web browser settings
The second issue was around symbolic links. I used symbolic links to link source from a repo into the framework hierarchy. This meant the eclipse project explorer saw one file (the symbolic path) and the debugger saw another (the 'rela' path inside the repo). So breakpoints set in the php explorer version of the file were not seen by the debugger. I solved this by checking out the repo beside the framework directory, symlinking my repo folders into the framework as before but using eclipse 'exclude from build path' on the symlinks so that both php explorer and debugger saw the real path to the file