Apologies if this is the way that it's supposed to work. I was unable to find a clear explanation of this in the docs (perhaps I did not look hard enough).

xdebug_dump_function_profile() does not appear to aggregate information about class methods into one line of output like it does for regular functions. I'm debugging a large complex application which makes extensive use of object oriented PHP and I'm trying to figure out which methods are taking up the most CPU time.

I've boiled it down into a simple example. If I run this code:

<?php

class MyClass {
function myMethod() {
; // do nothing
}
}

function MyFunction() {
$y = "blah";
}

xdebug_start_profiling();

$myClass = new MyClass();
for ($i = 0; $i < 20; $i++) {
$myClass->myMethod();
MyFunction();
}

xdebug_dump_function_profile(2);
?>

on XDebug 1.3.0 (there isn't an option for 1.3.0 in the pulldowns when I enter a bug, btw -- only 1.3.0rc1 and 1.3.0rc2) I find that it gives me one line for "MyFunction" but 20 individual lines for myMethod().

I can probably work around this by retrieving the data in array form and aggregating it myself (and I'll probably wind up doing that) but it seems natural that XDebug should do this for me.

Am I doing something wrong? Thanks!