0000693: Profiling: cachegrind files not written when filename exceeds 260 characters

ID	Project	Category	View Status	Date Submitted	Last Update
0000693	Xdebug	Uncategorized	public	2011-05-14 16:26	2016-12-23 21:26

Reporter	relaxnow	Assigned To
Priority	normal	Severity	minor	Reproducibility	always
Status	resolved	Resolution	no change required
Platform	x86	OS	CentOS	OS Version	5.6

Summary	0000693: Profiling: cachegrind files not written when filename exceeds 260 characters
Description	When the '%R' option is used for the output name and the request URI exceeds 260 characters XDebug doesn't output a cachegrind file or even log an error.
Steps To Reproduce	Set up XDebug, enable profiling. Use the following INI settings: xdebug.profiler_enable = 1 xdebug.profiler_output_name = cachegrind.out.%H.%R Go to a long url (I used ??11111111111111111111111111111222222222222222222222222222222233333333333333333333333344444444444444444444444444444444444455555555555555555555555555555566666666666666666666666666666666666667777777777777777777777777778888901234) Go to the output directory, expect to see a cachegrind.out file.
Additional Information	Attached is a patch made on a checkout of revision 3440 of trunk. This is my first C code ever, so it's probably too naive, but it does seem to fix the bug by truncating the filename to NAME_MAX. Let me know how I can help (had fun messing with C).
Tags	No tags attached.

Operating System
PHP Version	5.3.3

derick 2011-08-13 18:03 administrator ~0001781	Fixed for 2.1.3 and 2.2.

relaxnow 2011-10-12 06:56 reporter ~0001842	Tested this with current master from GitHub (https://github.com/derickr/xdebug/commit/00a00ea4512d414f0592675a7c91f5791868eb1a), was not fixed, applying the patch still fixed it.

derick 2016-11-28 21:28 administrator ~0003828	I still can't reproduce this. Is this still causing an issue for you?

derick 2016-12-23 21:26 administrator ~0004100	Closing this, as the requested feedback whether it's still a problem wasn't answered. Please reopen this issue if necessary.