| Updates to Xdebug Support within PDT. [message #59818] |
Mon, 29 October 2007 08:45  |
Eclipse User |
|
|
|
For all those who are interested in XDebug support in PDT, I thought I would quickly list the
changes made that should make it into PDT 1.0.1 M1.
1. fixed expression view so that expression results are not modifiable
2. fixed the URL dialog to have the previous value show up as the latest (not xdebug specific)
3. Stop URL uses the NO_EXEC version, so script not re-executed
4. fixed issue where strings containing base64 code were decode to bytes using the wrong encoding.
5. xdebug support should be more robust to unexpected and incorrect flows from xdebug itself
6. fixed the variables view so that it doesn't keep refreshing and collapsing arrays/objects
7. break on first line checkbox honoured correctly in EXE launch
8. working directory for an EXE launch will be the same as the script location if the environment
variable "XDEBUG_WORKING_DIR" is defined in the EXE launch. This can be set to anything, and is
a temporary workaround until the EXE launch can have a proper GUI option to select the working directory
9. With a Web script launch you should now be able to select a just a project or folder and the
automatic path mapping work the same as if you have selected a specific file.
10. Debugging multisession support - This is not enabled by default, but will allow you to have
multiple web script debug sessions running concurrently. I have yet to write this up in the document
on using XDebug, but will do so in the future.
Look forward to getting some feedback on these changes.
Dave Kelsey
|
|
|
|
| Re: Updates to Xdebug Support within PDT. [message #59916 is a reply to message #59868] |
Tue, 30 October 2007 03:24  |
| Eclipse User |
|
|
|
Originally posted by: dkel50.hotnospmail.com
Martin Eisengardt wrote:
>> 10. Debugging multisession support - This is not enabled by default, but
>> will allow you to have
>> multiple web script debug sessions running concurrently. I have yet to
>> write this up in the document on using XDebug, but will do so in the
>> future.
>
> Some question. Will a second session use a different url (different
> parameters)?
>
>
It doesn't have to be the same URL, it can be different (or the same
with different parameters), but there are some limitations.
1. you cannot debug the URL by invoking another launch (the URL must be
invoked in a different way, eg by hand, by java script, by some external
program).
2. If you are debugging the initial script and want to enter a URL into
say another tab in fire fox you will need to add
XDEBUG_SESSION_START=ECLIPSE_DBGP as a parameter to the URL (as the
cookie doesn't get set in the browser until the 1st script completes and
xdebug would not attempt to start a debug session)
3. The original launch will need to use a project or folder name and
further URL invocations need to invoke scripts in the same project or
folder for path mapping to work.
The multisession support was provided to address some specific
scenarios, so it would be good to get feedback on its use to see if
other scenarios are required and how it could be improved to support them.
Dave Kelsey
|
|
|
Powered by
FUDForum. Page generated in 0.06686 seconds
Home