This isn't a "problem", as I'm very familiar with the fact that DBG and eAccelerator don't play nice together, as I've been using phpEd for years now.

The question is simply; Is there any way to make them operate concurrently?

Also, (something I haven't tried yet) is disabling eAccelerator via .htaccess [i.e. php_flag eaccelerator.enabled 0] enough to allow DBG to run normally under a single vhost? One of the reasons that I ask this is that my fellow developers and I share a (large) machine. They don't use DBG (most of them run Mac or Linux), but they want eAccelerator installed to match our production environment. I, however, want the option to run both (separately, or concurrently if there's a way). Currently I've been doing my DBG sessions on a separate machine, but this makes things much more complicated.

Hrm.



Well, I guess that answers both questions. Sadly, I thought that the second one was actually feasible.

PHPInfo snapshot:

You want to debug your code right?
To make a code be debugged it have to be executed, right?
Hense, you have to turn eAccelerator off because it caches code and removes all debugging info from it
And honestly, debugger has nothing to do with this situation.

If eAccelerator is a supported product, please ask them to contact me or provide their contact info so I'll contact them and we'll find a solution on how to live together

I can understand that answer in response to the first question, however the second (as to whether disabling eAccelerator would be enough) seems to have changed. Contacting them is done via their mailing list - http://lists.sourceforge.net/lists/listinfo/eaccelerator-developers.

In prior releases of phpEd/DBG, the "eAccelerator is an unsupported product" message never appeared, and (it seemed, at least, that) DBG would load side-by-side with it, even if it wouldn't run.

It seems like the second situation should be supported, but for user-support reasons you added the eAccelerator check to reduce the number of user problems with it. Is that correct?

If so, would it be possible to make the eAccelerator check not simply on whether the module is loaded or not, but whether it is actually active. By setting eaccelerator.optimizer to 0 and eacclerator.enable to 0, the module is loaded, but completely disabled. This is something that can be done on a VHost or Directory level in Apache, which would allow situations like mine - operating on a shared server where eAccelerator is installed, but disabling it on a site-by-site or directory-by-directory basis for debugging.

Strictly speaking eAccelerator should just not do one little thing and I'll them about it and hopefully it will be enough.