View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000532 | Xdebug | Uncategorized | public | 2010-02-04 23:24 | 2010-02-17 00:32 |
| Reporter | bbence | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0000532: XDebug breaks header() function | ||||
| Description | I use:
And the following PHP code: '; Expected result is the following HTTP header: Actual result is this: Screenshots: With php_xdebug-2.0.5-5.3-vc6.dll (WORKS PROPERLY): | ||||
| Tags | No tags attached. | ||||
| Operating System | Windows 7 RC | ||||
| PHP Version | 5.3.1 | ||||
|
|
Confirming the above - I'm having the very same issue using the following setup:
It looks that no HTTP headers from PHP reach the browser (even the X-Powered-By header is missing) - this way location headers or content type charset settings don't work at all. |
|
|
I'm also experiencing this issue (obviously cookies / cookie based sessions don't work correctly without headers) Exactly the same setup as jotta, with code that boils down to: var_dump($_COOKIE['test']); Expected Result: Actual Result: Issues goes away when xdebug is not loaded. |
|
|
Good news, I can reproduce this (With Apache from apache.org, and PHP 5.2.13dev VC6 with Xdebug 2.1.0beta3-dev). Bad news, no clue why this happens yet :-) |
|
|
Expecting same bug on Windows 7 RTM Professional 32-bit with php 5.3.1 VC9 and xdebug beta2. I hope it will be fixed soon, because it is so boring to work without debug =( |
|
|
I was be able to reproduce this on Linux in a threaded environment as well, and I've just uploaded new Windows binaries to http://xdebug.org/files/xdebug-latest.tgz which should contain a binary that has this issue fixed. Could you please verify this as well? (The binaries should also fix another crash bug) |
|
|
Works for me: |
|
|
Thanks Derick! Variables in local scope (0000002) are all still reporting as undefined. |
|
|
Closing, as this seems fixed now. @mpanciera contact me through the mailinglist with a remote debug log (See http://xdebug.org/docs/remote#remote_log on how to make one) |