Bug 329496

Description Stu 2010-11-04 17:21:13 EDT

When this bug occurs:
While using XDebug with remote debugging any PHP script from the command-line with env var XDEBUG_CONFIG="idekey=ECLIPSE_DBGP".
This bug also occurs when you're debugging PHP via a web browser, doesn't matter really.

Repro steps:
1. Create a file main.php with some code in it that also includes a file called inc.php that has some other code in it.
2. I'm assuming a project directory has been set up for these files, in our case inc.php is in a child folder from main.php
3. Open inc.php in Eclipse
4. Set a breakpoint in that file
5. Run the main.php from the command-line so that the breakpoint will hit in Eclipse.

Resulting Issues:
+ The breakpoint will hit in Eclipse, but the debugger will open a NEW instance of the inc.php window instead of using the existing window.
+ You can only enable or disable breakpoints from the original instance of inc.php's editor.
+ In the Breakpoints panel, you'll now see two breakpoints, one with: inc.php [line: XX] and another with a full path like: /website/docs/mytest/includes/inc.php [line: XX]

All server paths seem to be appropraitely mapped to the web site location on the local hard drive (for example: /website/docs/mytest/ ).
My partner and I have both experienced with with Eclipse for PHP Developers on both Mac OSX and Windows 7 versions of Eclipse.
This bug has occurred in older versions of PDT as well (we've seen it with 2.1 and 2.2).


-- Configuration Details --
Product: Eclipse 1.3.1.20100913-1228 (org.eclipse.epp.package.php.product)
Installed Features:
 org.eclipse.platform 3.6.1.r361_v20100909-9gF78GrkFqw7GrsZnvz0JWNTeb6fue6896L