Summary: | ld.so error in valgrind (nptl system) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stephen Amar <acetik85> |
Component: | Current packages | Assignee: | Maurice van der Pot (RETIRED) <griffon26> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | f5d8fd51ed1e804c9e8d0357e8614e0493b06e96 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Stephen Amar
2004-12-24 09:57:53 UTC
I'm runing a non-nptl system but get similar errors. But this ain't the first valgrind version to yield such errors - it started quite a while ago... I got used to it and just ignore them - but it would really sweet to see them removed... The reason that these messages show up is probably that glibc/ld is stripped. Valgrind's default suppression files for glibc specify the messages to suppress using function names. I'll check some more next week. I double checked and what I said was correct. If you really want to suppress any warnings from ld for instance, you can write a suppression with lines like this one: obj:/lib/ld-2.3.4.so Or you could decide not to strip glibc and check if the default glibc suppression file does the job. Check the valgrind documentation on suppressing errors for more details: http://developer.kde.org/~sewardj/docs-2.2.0/coregrind_core.html#suppress Note: by suppressing everything from system libraries, you may mask bugs in your own programs. If you pass a string with uninitialised values to printf, valgrind will only tell you something is wrong when it is executing code in glibc. If you suppress everything from glibc, you won't get anything at all. ok, how to tell glibc not to strip? or maybe even more preferably just not to strip 'ld' ? |