102157 2005-08-11 14:46 0000 valgrind hangs on stertup/exit on gentoo kernel 2005-08-31 01:28:40 0000 1 1 1 Unclassified Gentoo Linux Ebuilds unspecified All Linux RESOLVED FIXED http://bugs.kde.org/show_bug.cgi?id=109861 P2 normal --- 1 dizzy@roedu.net griffon26@gentoo.org kernel@gentoo.org Samuele.Kaplun@cern.ch trapni@gentoo.org dizzy@roedu.net 2005-08-11 14:46:46 0000 Hi Please see the bug from the mentioned URL! PS: I know this is also because of some memory management "tricks" valgrind people do and they want to recode the memory management for this and other reasons but whould be nice if gentoo whould come with some fix/workarround as gentoo kernel makes the problem very worse (maybe gentoo kernel people can look into it too). Thanks! griffon26@gentoo.org 2005-08-12 12:03:43 0000 It seems some of gentoo-sources' patches are causing a delay in m(un)map for valgrind. If anyone in the kernel team has some time to take a look at the kde bug report (see url field), then please do. dsd@gentoo.org 2005-08-12 12:26:07 0000 Has anyone confirmed that its actually the gentoo patchset making a difference (i.e. compared vanilla-sources-2.6.12 to gentoo-sources-2.6.12)? griffon26@gentoo.org 2005-08-12 15:32:24 0000 Christian, I'm sure you don't mind being put on the cc of this bug as well. Can you answer dsd's question? Does the problem disappear with a vanilla kernel? trapni@gentoo.org 2005-08-12 17:08:46 0000 Heya, so far I can confirm that the behavior still occurs on * hardened-sources-2.6.11-r15, and * gentoo-source-2.6.12-gentoo-r6 I need to get a vanilla built up first; (man, I hate rebooting ;) hold on. trapni@gentoo.org 2005-08-12 18:12:07 0000 vanilla-sources-2.6.13_rc6 doesn't speedup VG either :( dizzy@roedu.net 2005-08-13 07:34:55 0000 Uh... sorry, I got confused from the original bug report that somehow it was a gentoo kernel only issue, I should have tested vanilla before posting here. I posted this bug because I thought it's a gentoo kernel issue or some kind of gentoo particular issue because so far on valgrind bugtracker there are 2 persons who complained about this, both having gentoo :) I also commented on the valgrind bug tracker that it affects vanilla, this should raise the priority of this problem (but still whould be interesting to find out why the FC kernel doesn't seem to display this bug). griffon26@gentoo.org 2005-08-14 11:38:01 0000 Alrighty then, marking RESOLVED/UPSTREAM. Please add any extra non-gentoo specific comments to their bug report. griffon26@gentoo.org 2005-08-30 12:59:11 0000 *** Bug 103898 has been marked as a duplicate of this bug. *** griffon26@gentoo.org 2005-08-30 13:04:29 0000 Reopening to fix status griffon26@gentoo.org 2005-08-30 13:05:16 0000 Should be fixed in valgrind-3.0.1, which was just added to portage. Thanks for reporting the problem, Dizzy. trapni@gentoo.org 2005-08-30 15:28:10 0000 are you sure that 3.0.1 has a fix for it? I mean, I remember some VG dev telling me, that this fix *will* require major changes to the address manager of VG, though, this wouldn't be part of 3.0.x-line of course (it's a seperate branch even). But this address manager rewrite isn't the only reason for rewriting it (think of the glibc independency in stage2 etc)... can someone approve it is working for him by now? (having 3.0.1 installed of course) griffon26@gentoo.org 2005-08-30 23:34:14 0000 It's not fixed in valgrind's source, it's fixed in the ebuild by not building with PIE anymore. dizzy@roedu.net 2005-08-31 01:28:40 0000 I can confirm it works very nice now :) (only used it on my new project for 5 minutes to test it out and already found a bug hehe)