The development environment:

- PHPEd 3.3.1 Build 3358
- Apache 2.0.44 on Linux
- PHP 4.3.1
- DBG 2.16.7 for PHP 4.3.1

The server root is mapped via Samba and available as network drive.

On the server: /srv/wwwroot/htdocs
Locally on the client N:\ (-> points to the web root)

When starting the debug session, only the _first_ page goes through the debugger - nearly _all_ other pages are just opened without the debugger.

The first page is: http://server/functions/phonelist.php

This pages calls directly via a link: http://server/global.php?mode=new

Well - all breakpoints in global.php and all subsequent files, which are included there are completely ignored and also the output of PHP is not displayed.

Once it got a bit better, after we created a new workspace and a new project - but only for a while - now debugging is nearly impossible (

We checked the php.ini on the Server and we also enabled cookies on the local browser and even added the URL of the debug server to the list of trusted sites in the browser.

Any hints? We already purchased a number of licenses as the evaluation really looked good - but the stability of the debugger seems really worse and depending on the source code :-/

How the 2nd page gets called ?
You mentioned , please be more specific. Also, please try to link this way to a page containing phpinfo() function call alone and send me the results at the address http://www.nusphere.com/contact_us/.

The call is a regular link:

<a href="global.php?mode=new">Create new</a>

During further tests, we found out, that sometimes either the debug cookie was not sent or the browser did send cookie back when requesting the next page. Another point we missed is defining the debugger port in PHP.INI. Well - after adding

debugger.port=7869, 10000/16

it seems to work much better. However - i still wonder a bit, since the debugger generally worked, but somehow not completeley. What does the "10000/16" mean here?

okay.
DBG uses "temporary" cookie which works with just one IE window, works for the same domain. If you open a new page in a new window it may not work. If you open a new page in a new domain it won't work too.
In any case you may run debug session if you follow these instructions.

Ok I have fixed my problem. I forgot that I had made some changes to how I had apache set up locally, and had modified some virtual hosts without making the related changes in the app I was debugging.

So in effect the debugger was being pointed to a different domain (http://localhost.newdomain/ from the original location of http://localhost/), which is why it lost the DBGSESSID.