[xdebug-general] Solved issue with no cachegrind files on Fedora/Centos

From: Kevin Hunt <kthunt[@]gmail.com>
Date: Fri, 13 Feb 2015 01:39:06 -0800

Hi, to start with, Xdebug installed without any issues and never generated
any errors in and of itself.

I'm working on an instance of Centos 7 (nginx, php-fpm) and had spent the
last couple hours banging my head against the wall trying to figure out why
everything looked correct and behaved as if it was working fine, but I
never saw any cachegrind.out files created in /tmp.

Finally I did a search for any cachegrind.out files on the system and they
turned up in:
  ./tmp/systemd-private-s2GkNY/tmp/cachegrind.out.1423818581

Seems there's a security feature on Fedora/Centos that creates private tmp
areas for processes that I was unaware of, and that is where they were
being put. After I discovered this I did some searching and looked here:
  http://robertbasic.com/blog/xdebug-and-private-tmp-on-fedora

Once I created a different folder to put the cachegrind.out files in
via xdebug.profiler_output_dir all was well. This would be a helpful note
to add in the install docs.

-kevin
Received on Fri Feb 13 2015 - 09:39:07 GMT

This archive was generated by hypermail 2.2.0 : Mon Jun 25 2018 - 06:00:04 BST