View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000407 | Xdebug | Profiling | public | 2008-09-05 11:18 | 2025-11-25 14:22 |
| Reporter | smoe | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | confirmed | Resolution | open | ||
| Target Version | 3.6dev | ||||
| Summary | 0000407: Profilerdumpfile name is always auto_prepend_file name | ||||
| Description | my php.ini: then the dumpfilename is always "cachegrind.out._path_to_prepend-php_prepend_php", regardless which script i requested | ||||
| Additional Information | Im using PHP5 as FastCGI | ||||
| Tags | No tags attached. | ||||
| Operating System | Gnu/Linux Debian Lenny | ||||
| PHP Version | 5.2.6 | ||||
| child of | 0002072 | acknowledged | Rewrite the profiler |
|
|
This bug still exists, and can be reproduced with the one liner: touch index.php start.php; php -dauto_prepend_file=start.php -dxdebug.profiler_output_name=^Cachegrind.out.%s -dxdebug.profiler_enable=1 index.php However, I don't see how I can figure our which script is the "auto prepend" script, or the normal script in PHP itself. |
|
|
I couldn't reproduce this now (3 years after so might have been fixed):
Gets 2 files:
bug00407.cachegrind.C__dev_git_php-7.3.3_ext_xdebug_tests_bug00407.prepend_php.out =
So, should this issue be closed? Do I need to commit the phpt? If so, I would like to know how to remove the two absolute paths I have in the phpt file (otherwise, it's gonna fail on everyone else's computer!) |
|
|
Check whether this is now fixed. |
|
|
This is still a problem, now with the reproducible new case: touch /tmp/prepend.inc && touch /tmp/test.php && php -n -dzend_extension=xdebug -dxdebug.mode=profile -dauto_prepend_file=/tmp/prepend.inc -dxdebug.profiler_output_name=bug00407.cachegrind.%s.out /tmp/test.php |