Valgrind, a GPL'd tool to debug applications' memory allocation, is one of the most exciting profiling tools in the free software world. Think Purify, but free, easier and available for Linux. Now Josef Weidendorfer makes Valgrind even more attractive with the first unofficial release of KCachegrind, a KDE front-end for Valgrind's profiling tool. (Click for screenshots of basic use and a call tree graph.) Now all x86 Linux developers can benefit from a professional grade profiling tool!

Hmm, what does this have to do with anything? That's great that those distros have Valgrind packaged, but I see an alterior motive in your post OTHER than just trying to be a friendly user :) The reason this isn't relavent is because Valgrind 1.0.1 in ANY distro needs some patches for some enhanced profiling. Oh, don't let me forget:

/me hands you a cookie for using Gentoo and Debian.

Nick Betcher

-----------------
Quote of the day:
"I'd like to get a refill for my meds." - patient
"I'm sorry sir, you're out of refills, we'll have to call your doctor." - pharmacy technician
"What are refills?" - SAME patient

The class KWidgetAction(...) is needed. But this class is new in KDE 3.1CVS
...so: without KDE 3.1 (if you have 3.0) you can only compile it if you just comment the line out in which KWidgetAction appears. (does not matter that much .. "just" the filter will disappear than)

Compiling with gcc 3.x gives a few errors, too. You have to remove the "=0" in the *.cpp files which the error-message tells you

Yes, it would be great :)
Maybe some day, it's kind of fun (and maybe a little sad...) to read this now:

"Gaël: Will there be a KEmacs?
Matthias: XEmacs is the editor of choice for many of the KDE developers. In converse, some XEmacs-developers also mentioned interest in a tighter KDE integration. So the future regarding KEmacs looks pretty bright."

What are you trying to say?! That the 1.0.1-patch doesn't apply to the 1.0.2 binary? Surprise! As I mentioned above, you can still download the 1.0.1 binary, too which the 1.0.1 applies quite well (surprise again!).

Well, the first thing I wanted to say is that 1.0.2 actually was there,
which your post seemed to imply that it was not.

I am not surprised... I am just stating facts, it's just that
*cachegrind* 1.0.1 is not working too well (which is why
Julian Seward released 1.0.2).
Also just so you know; patches can apply to newer versions,
it just depends on how the new version was changed...
much like a cvs merge can work without manual intervention,
a patch can work on a later version depending on what was modified
in the new version. Yes, it is not as "safe" as a tested patch
against a certain version but if you are not depending on it in a
production environment, and what you got does not work, why not try it?
And after I tried it I might tell others who are like of mind
so that they would know it would not work right of the bat...
Then you can decide if you want to do the patch manually in
the new code or just wait for someone to release a new patch...
For me cachegrind 1.0.1 gets an assert almost all of the time
but not with 1.0.2 (yes, unpatched).

> Well, the first thing I wanted to say is that 1.0.2 actually
> was there, which your post seemed to imply that it was not.

Oh well. My posting was the answer to Perra, who said "Problem is that
only Valgrind 1.0.2 is available now which your patch won't apply to."
I said that the link to 1.0.1 may have been removed, but the binary was
still there and posted the link. So there would be no problem to get
a working, patched cachegrind with a matching kcachegrind, even though
it wasn't the very last version. Then you =repeated= that the 1.0.1 patch
wouldn't apply to 1.0.2, which was already stated before and not really
surprising. Yes, my answer was a bit harsh, sorry. But it was easily
topped by two replies, presumably by the same child using different names
and with really bad manners. He should wash his mouth with soap. ;-)

Ok, trying to clarify (never been that good doing that lol)
When I read your statement "Only the 1.0.2 =link= is available now"
I thought that you had tried to access the 1.0.2 version during a transition,
ie the link to the 1.0.1 file was removed but the tar file was/is still there
and a new link had been added to the 1.0.2 tar file but the tar file it pointed
to was not uploaded yet (or temporarily removed).
So when I posted again the information I thought I provided was that
you can download it now + which files the patch failed for.
Also 1.0.1 cachegrind has never really worked for me.

Aaaaand.... as an example of patching sometimes working for closely related versions:
the patches V 0.2a and 0.1e both for valgrind 1.0.2,
should be used for 1.0.3.
quote from kcachegrind site:
"Update: Both Valgrind patches work for 1.0.3, too (There is one reject because of the wrong version number, which can be safely ignored)."