[xdebug-dev] Bug 0000140: Is the profiler output filename correctly documented?

The following NEW bug has been ADDED.
======================================================================
http://bugs.xdebug.org/bug_view_page.php?bug_id=0000140
======================================================================
Reporter: mccabe
Handler:
======================================================================
Project: Xdebug
Bug ID: 140
Category: Documentation
Reproducibility: always
Severity: trivial
Priority: normal
Status: new
Operating System: Linux
PHP Version: 4.3.10
Xdebug Version: 2.0-dev
======================================================================
Date Submitted: 2005-08-01 18:35 CEST
Last Modified: 2005-08-01 18:35 CEST
======================================================================
Summary: Is the profiler output filename correctly documented?
Description:
The profiling docs says
"The name of the generated file always starts with "cachegrind.out." and
ends with either the PID (process ID) of the PHP (or Apache) process or
the crc32 hash of the current working directory"

The last part, "crc32 hash of the current working directory", shouldnt
that be the "crc32 hash of the initially debugged script"?

At least thats what it looks like in the source.

======================================================================

Bug History
Date Modified Username Field Change
======================================================================
2005-08-01 18:35mccabe New Bug
2005-08-01 18:35mccabe Bug Monitored: mccabe
======================================================================
Received on Mon Aug 01 2005 - 18:35:53 BST