title: xdebug 3 profile on windows generates complete file paths confusing QCachegrind
body: <p>Xdebug 3.1.1 on Windows typically creates grind files with the following file description</p>
  <pre><code>fl=(3) D:\Projekten\dwh_php7\inc\utils.php
  fn=(5) require::D:\Projekten\dwh_php7\inc\utils.php
  1 110 0
  </code></pre>
  <p>with other words it includes the complete path to the source file (not a relative one). This confuses QCachegrind (0.7.4) in finding the source code. It seems to prepend the path of the grind file itself to the path it finds inside cgrind file yielding something like
  <code>Y:/Temp/D:\Projekten\dwh_php7\inc\utils.php</code> which obviously is <strong>not</strong> the location of the source code. Moving the grind file to the project folder generates this <code>D:/Projekten/dwh_php7/\Projekten\guerbet\dwh_php7\inc\utils.php</code> which is also not helpful.</p>
  <p>How do I explain to Xdebug not to store the complete source path in the cgrind files?
  The developer of qcachegrind was helpful enough to point out that this is the way it is supposed to work. But perhaps this is a thing that got lost in translation from *nix to windows.</p>
  <p>Btw. the Project path is setup as a virtual directory in Apache.</p>