On Wed, 26 Nov 2008, tic tac wrote: > I have a question about the *.supp files located in the source tree > after configure and under lib/valgrind in the runtime tree after > install. Are those used for compilation at all (I looked quickly at > the Makefile and it does not seem like it ..)? Are they used at > runtime and in which fashion (static or dynamic library linking)?
They are read at run-time by Valgrind. When Valgrind detects an error, it consults the file contents to decide if the error should be displayed. There's no relation to compilation of any kind. > My main concern is that I am running binaries that are already using glibc > and I would like to make sure that neither valgrind compilation or runtime > is modifying the existing glibc libraries. Depends what you mean by "modifying". Valgrind makes huge modification to all code that is run, including libc, but it's all done in memory. The libraries on disk aren't modified. Nick ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
