|
From: Oswald B. <os...@kd...> - 2004-08-09 14:29:47
|
On Mon, Aug 09, 2004 at 02:28:29PM +0100, Nicholas Nethercote wrote: > On Thu, 5 Aug 2004, Oswald Buddenhagen wrote: > >>Why is it bad for distributors? > >> > >multiple kernels (with different PAGE_OFFSETs), one valgrind (configured > >for a specific PAGE_OFFSET). hmmm ... > >sure, it's not different from the current situation, so i don't expect > >the stream of puzzled failure reports to widen ... > > I'm not sure I understand. If it's set up at configure-time, why is it a > problem for distributors? > > The only problem I can see with a configure-time setup is if a person has > more than one kernel on the same system, or changes their kernel's memory > layout. But Valgrind could check at startup that the memory layout > matches what it saw at configure-time, and abort/warn if it doesn't. > Or is there a problem here that I'm not seeing? > only the correlation. ;) distribs can either build a valgrind that runs on any kernel (well, with, say, PAGE_OFFSET >= 1gb) and heavily restrict the memory available to valgrind for all users, or they can build one for PAGE_OFFSET=3g (or even 3.5, fwiw), but exclude the users with a lower PAGE_OFFSET (like they do currently). the only (linux) distributor that would have no problem with this would be gentoo, as they ship only sources ... -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Chaos, panic, and disorder - my work here is done. |