XDebug profiling in PHP - can't get output

Question

I've got a strange issue. I've setup XDebug to profile a PHP application we're working on. I believe everything is setup correctly but I get no output when I run it. My configuration looks like this:

zend_extension="/usr/local/lib/php/extensions/no-debug-non-zts-20060613/xdebug.so
[XDebug]
xdebug.profiler_append = 1
xdebug.profiler_enable = 0 (I've tried this both on and off)
xdebug.profiler_enable_trigger = 1
xdebug.profiler_output_dir = "/debug/xdebug/profiler_output_dir"
xdebug.profiler_output_name = "cachegrind.out.%p"

All the phpinfo() settings match up like they should. The permissions on the output directory are set to 777 right now just so I can test it. I've tried using a directory under public_html as well but no luck. The URL I'm using to launch the profiler is:

http://example.com/my_page.php?XDEBUG_PROFILE
-or-
http://example.com/my_page.php?XDEBUG_PROFILE=1

Neither works. Any help would be GREATLY appreciated!! This app has a 5-6 second page load time and I haven't been able to trace it through code.

score 18 · Answer 1 · edited Jul 12 '19 at 00:42

18

There is also problem with /tmp folders on some distributions, i couldnt get output on centos 7 and then i found this

So, i have set

xdebug.profiler_output_dir=/home/jirka/profile

chmod 777 /home/jirka/profile and its ok now.

edited Jul 12 '19 at 00:42

Jonathan

6,741
7
52
69

answered Oct 23 '14 at 07:50

Aiphee

8,904
3
18
16

3

There's more information about that `PrivateTmp` setting [here](https://securityblog.redhat.com/2014/04/09/new-red-hat-enterprise-linux-7-security-feature-privatetmp/). It "sets up a new file system namespace for the executed processes and mounts a private `/tmp` directory inside it, that is not shared by processes outside of the namespace. This means that processes running with this flag would see a different and unique `/tmp` from the one users and other daemons sees or can access." – TachyonVortex Feb 04 '15 at 17:42
Thanks for this. It turns out my OpenSUSE 13.1 has the same configuration and moving the profiler output elsewhere solved the problem. – savedario Apr 05 '15 at 10:33

score 11 · Accepted Answer · answered Aug 22 '10 at 12:50

11

Comment out xdebug.profiler_output_dir and xdebug.profiler_output_name and see whether you can find the output under /tmp/.

answered Aug 22 '10 at 12:50

Hamid Nazari

3,905
2
28
31

3

Hamid, Turns out you were on the right track. I'd forgotten to put the full path to the output directory. Here's the final solution: xdebug.profiler_append=1 xdebug.profiler_output_dir ="/home/username/debug/xdebug/profiler_output_dir" xdebug.profiler_output_name = "cachegrind.out.%s.%H" – John Swaringen Aug 23 '10 at 17:51

score 6 · Answer 3 · answered Dec 20 '11 at 12:23

6

Another possible cause of this issue is the permissions on the folder of profiler_output_dir.

Adding write permissions to the group and owner resolved the issue for me:

sudo chmod go+w /home/dimitris/cachegrind/

answered Dec 20 '11 at 12:23

Dimitris Baltas

3,115
3
34
26

score 1 · Answer 4 · answered Apr 04 '17 at 09:05

1

The full path was required, not just the path:

xdebug.profiler_append=1
xdebug.profiler_output_dir ="/home/username/debug/xdebug/profiler_output_dir"
xdebug.profiler_output_name = "cachegrind.out.%s.%H"

answered Apr 04 '17 at 09:05

k0pernikus

60,309
67
216
347

Note: This was the solution provided by the OP in their question. – k0pernikus Apr 04 '17 at 09:07

score 1 · Answer 5 · answered Mar 21 '12 at 16:29

1

Also, beware of access restrictions, such as access rights, groups, owner and SElinux...

answered Mar 21 '12 at 16:29

greg

696
1
9
16

Indeed. Had same problem with apache not being able to write to defined user directory because of permissions – Artjom Kurapov Jul 05 '12 at 09:48

XDebug profiling in PHP - can't get output

5 Answers5

Linked