|
From: Olly B. <ol...@su...> - 2003-10-16 20:16:39
|
On Thu, Oct 16, 2003 at 09:31:58PM +0200, Dirk Mueller wrote:
> well, then there would be not much point in checking at compile time at all.
Perhaps the small program which is currently built and run at configure
time to check for NPTL should actually be built and installed (e.g. as
/usr/lib/valgrind/nptlcheck) and then run from the valgrind wrapper
script?
AIUI, at present if the user builds and installs valgrind using a
non-NPTL kernel and then upgrades to an NPTL kernel, valgrind won't
disable NPTL. That seems a fairly common scenario. It'll also fail to
disable NPTL if the user installs a valgrind package (RPM, deb, etc)
built on a non-NPTL kernel machine.
Cheers,
Olly
|