View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000220 | Xdebug | Uncategorized | public | 2006-11-21 13:28 | 2006-11-27 21:54 |
| Reporter | d_kelsey | Assigned To | |||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | unable to reproduce | ||
| Summary | 0000220: PHP.exe crashes when the script ends | ||||
| Description | This bug can also be reproduced on PHP 5.1.4. I have 2 scripts testcase3.php<?php echo var_dump($a); file1.php<?php
echo 'hello'; $a='Well hello There'; phpinfo(); ?> Using the debug client I enter the following commands cmd setbreakpoint_set -i 25 -t line -f file:///C%3a/temp/xdebugBug/testcase3.php -n 18 A problem is then reported by Microsoft windows and offers me the option to send or don't send the report to Microsoft | ||||
| Additional Information | Note that it is important that you must set both breakpoints even though file1.php is never called. You must do the feature set and you must do a context get. It is always reproduceable using this set of commands and these files. I have tried other files and only setting a single break point and the problem doesn't occur. I can stop the problem by setting the max_depth to 10 (for example) or by not setting max_depth at all (but I need to allow a user to specify max_depth). if I set max_depth to a value of 4, then I get the trap when I attempt the context_get command. I have not tried any other value of max_depth apart from 10. | ||||
| Tags | No tags attached. | ||||
| Operating System | Windows XP | ||||
| PHP Version | 5.2.0 | ||||
|
|
I tried to reproduce this on LInux (with valgrind) with php 5.2.0 and the latest CVS release of Xdebug, but I couldn't find a single memory corruption issue (which is what your report would suggest). Perhaps you could try the latest snapshot version? (from http://pecl4win.php.net/ext.php/php_xdebug.dll) |
|
|
ok, a new day a reboot of the machine and now I cannot recreate the problem, strange because when debugging with my client I observed the problem and PHP script was being launched in it's own process every time and was recreatable every time. I recreated the issues outside of my debug environment with the xdebug client, but I cannot recreate it now in that environment either. Maybe I managed to have a rogue extension somewhere being loaded ? |
|
|
That is possible as windows keeps dlls in memory. I will close the report now, but feel free to reopen if you can recreate it. |