faq  flatforty  contribute  subscribe  configure  search  rdf  main  parent	New version of KCachegrind available... by Josef Weidendorfer on Wednesday 04/Sep/2002, @17:35 Hi, I just uploaded new versions KCachegrind 0.1b and valgrind-1.0.1 patch 0.1b. Look at the News section of the webpage for changes. And please give it a try. I should have all known bugs fixed :-) Happy profiling, Josef	Related Links  ·   Articles on Developer  ·   Also by Josef Weidendorfer  ·   Contact author Thread Threshold: 10 comments 20 comments 30 comments 40 comments 50 comments 60 comments 70 comments 80 comments 90 comments 100 comments 110 comments 120 comments 130 comments 140 comments 150 comments 160 comments 170 comments 180 comments 190 comments 200 comments 300 comments 400 comments 500 comments 1000 comments
	The Fine Print: The following comments are owned by whomever posted them. ( Reply ) Re: New version of KCachegrind available... by Perra on Friday 06/Sep/2002, @02:36 Problem is that only Valgrind 1.0.2 is available now which your patch won't apply to :) [ Reply To This | View ] Re: New version of KCachegrind available... by dnm on Friday 06/Sep/2002, @02:47 Yeah, the patch for 1.0.1 fails on 1.0.2... But one would hope for a synch between valgrinds cachegrind and kcachegrind so that the patch will not be necessary. [ Reply To This | View ] Re: New version of KCachegrind available... by Melchior FRANZ on Friday 06/Sep/2002, @03:20 Wrong. Only the 1.0.2 =link= is available now. But the 1.0.1 archive is still there: http://developer.kde.org/~sewardj/valgrind-1.0.1.tar.bz2. [ Reply To This | View ] Re: New version of KCachegrind available... by dnm on Friday 06/Sep/2002, @05:19 Uhm, I downloaded the 1.0.2, it IS (or was) there, I tried to apply the patch for 1.0.1 in the 1.0.2 directory and it fails. The patch does apply to the 1.0.1 directory without complaining. cut from rpm-build ----------------------------------------------------- -rw-r--r-- 501/501 105 2002-06-05 22:28:33 valgrind-1.0.2/tests/nanoleak.c -rw-r--r-- 501/501 491 2002-06-19 12:17:40 valgrind-1.0.2/tests/pth_pause.c -rw-r--r-- 501/501 996 2002-06-20 10:17:07 valgrind-1.0.2/tests/pth_sigpending.c -rw-r--r-- 501/501 2311 2002-08-25 22:02:25 valgrind-1.0.2/tests/pth_atfork1.c + STATUS=0 + '[' 0 -ne 0 ']' + cd valgrind-1.0.2 ++ /usr/bin/id -u + '[' 505 = 0 ']' ++ /usr/bin/id -u + '[' 505 = 0 ']' + /bin/chmod -Rf a+rX,g-w,o-w . + echo 'Patch #0 (patch-0.1c-valgrind-1.0.1):' Patch #0 (patch-0.1c-valgrind-1.0.1): + patch -p1 -s 1 out of 1 hunk FAILED -- saving rejects to file configure.in.rej 14 out of 35 hunks FAILED -- saving rejects to file vg_cachesim.c.rej 3 out of 6 hunks FAILED -- saving rejects to file vg_include.h.rej 1 out of 5 hunks FAILED -- saving rejects to file vg_main.c.rej 2 out of 14 hunks FAILED -- saving rejects to file vg_symtab2.c.rej 2 out of 2 hunks FAILED -- saving rejects to file vg_syscall_mem.c.rej error: Bad exit status from /var/tmp/rpm-tmp.71239 (%prep) [ Reply To This | View ] Re: New version of KCachegrind available... by Melchior FRANZ on Sunday 08/Sep/2002, @06:42 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!). [ Reply To This | View ] Re: New version of KCachegrind available... by dnm on Tuesday 10/Sep/2002, @02:31 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). [ Reply To This | View ] Re: New version of KCachegrind available... by Melchior FRANZ on Tuesday 10/Sep/2002, @03:44 > 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. ;-) [ Reply To This | View ] Re: New version of KCachegrind available... by Melchior FRANZ on Tuesday 10/Sep/2002, @03:56 ... but meanwhile there's a 1.0.2 patch anyway. Thank you, Josef! :-) [ Reply To This | View ] Re: New version of KCachegrind available... by dnm on Wednesday 11/Sep/2002, @06:12 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. I will go try the new patch now though! [ Reply To This | View ] Re: New version of KCachegrind available... by dnm on Tuesday 24/Sep/2002, @08:21 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)." (Yes, I have tested this and it works) [ Reply To This | View ] Re: New version of KCachegrind available... by bloemist on Sunday 08/Sep/2002, @07:06 you're not too bright aren't you? [ Reply To This | View ]   The Fine Print: The previous comments are owned by whomever posted them. ( Reply )

		"You would know that after informal research, KDE developers prefer tea!" -- Roberto Alsina
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.

[ home | post article | flat forty | subscribe | search | rdf ]