-
Closing. Duplicate of bug 2886569.
BTW, this bug tracker is really bad. Better use bugs.kde.org for reports.
2009-10-27 13:28:50 UTC in KCachegrind Profiler Frontend
-
Followup: some clarification...
> /usr/share/doc/kdelibs3-devel-3 is the location of the kde3 lib files ...
This path does sound very wrong. In /usr/share/doc usually only documentation is installed.
If you want to install KDE3 development packages, you should check for packages
kdelibs3 to get the shared libraries (usually in /usr/lib) *and* kdelibs3-devel for the
header files (note...
2009-10-27 13:25:43 UTC in KCachegrind Profiler Frontend
-
Somehow you are mixing library versions. KDE3 libaries are not compatible to KDE4 libraries.
Your configure output shows me that you tried to compile the KDE3 version of kcachegrind from source. However, with only KDE4 libraries (kdelibs-4.3.1-3.fc10.x86_64) installed, this can not work. Therefore the error.
Why not simply use the KDE4 version of kcachegrind which should be provided by your...
2009-10-27 13:07:21 UTC in KCachegrind Profiler Frontend
-
The number of drawing requests to the X server done by an application has nothing to
do with its size/purpose. Also, as this is hidden by the tool kits API (in this case Qt), I can only assume what will make it better. It would help if you say whether this is about the KDE3 or KDE4 version.
Does it help to switch off the shading in the Caller/Callee map visualizations (Context...
2009-09-07 08:49:48 UTC in KCachegrind Profiler Frontend
-
I do not support xdebug. Please talk to the author of
xdebug regarding this issue.
2008-12-24 13:26:32 UTC in KCachegrind Profiler Frontend
-
> I was more or less expecting --seperate-callers=infinity to be the
> default, but then combine the samples in the per-function view.
The exponentially growing number of different call paths forbids
such behavior in general. Callgrind observes every path executed,
not just some samples. E.g. just a startup of firefox already
gives a few million call paths with --seperate-callers=20. And...
2008-05-13 11:09:44 UTC in KCachegrind Profiler Frontend
-
I see no obvious bug in the attached result file.
What did you expect to be different?
Remember that in a call graph every function appears only
once, and you get a superposition of all call paths. Callgrind
collects the exact cost of functions and call arcs between
functions. This is different from path profiling, where cost is
attributed to call chains. However, callgrind can do this...
2008-05-09 14:28:56 UTC in KCachegrind Profiler Frontend
-
Logged In: YES
user_id=621915
The maximal number of entries in lists is limited to
make the GUI more snappy. It is assumed that only the
top entries are interesting, ordered according to the
cost of the functions.
Neverless, your data was fully loaded. They will
be shown in the caller/callee lists and the call graph
if they are relevant.
If you know what you are searching for, you get...
2006-11-14 11:18:00 UTC in KCachegrind Profiler Frontend
-
weidendo committed patchset 277 of module kcachegrind to the KCachegrind Profiler Frontend CVS repository, changing 6 files.
2006-08-21 18:07:10 UTC in KCachegrind Profiler Frontend
-
weidendo committed patchset 276 of module kcachegrind to the KCachegrind Profiler Frontend CVS repository, changing 1 files.
2006-08-20 16:52:17 UTC in KCachegrind Profiler Frontend
