valgrind is generating warnings on /lib/ld-2.3.5.so

Tested with the upstream valgrind-3.0.1 with the same result...

I think this is caused by this valgrind version being out of sync with our glibc version, as it has an internal list of things to ignore.

Any plans to update it ? It its not done by someone else I will eventually look on how to complete the ignore list, I use valgrind a lot....

How is this still unconfirmed?

I believe this should be applied on the other independent files. I have applied to the default because I am sure it is reading this one and the included patch did work for the warnings I was able to detect...

I'll take care of getting this fixed... thanks for reporting

This should be the correct fix for the problem... only waiting for someone to confirm that this fix is correct

That is a partial fix, it will not catch other warnings relating to dlopen (I have experimentd this with my own application wich uses dlopen for the modules load).
They are very similar to other suppressions already listed for debian (dl_open*), the exact match for both cases was obtained from the warnings I got with ubuntu dapper...

+{
+ Ubuntu_dlopen
+ Memcheck:Cond
+ obj:/lib/ld-2.3.6.so
+ obj:/lib/ld-2.3.6.so
+ obj:/lib/tls/i686/cmov/libc-2.3.6.so
+ obj:/lib/ld-2.3.6.so
+ fun:_dl_open
+ obj:/lib/tls/i686/cmov/libdl-2.3.6.so
+ obj:/lib/ld-2.3.6.so
+ obj:/lib/tls/i686/cmov/libdl-2.3.6.so
+ fun:dlopen
+}
+
+{
+ Ubuntu_dlopen_2
+ Memcheck:Cond
+ obj:/lib/ld-2.3.6.so
+ obj:/lib/tls/i686/cmov/libc-2.3.6.so
+ obj:/lib/ld-2.3.6.so
+ fun:_dl_open
+ obj:/lib/tls/i686/cmov/libdl-2.3.6.so
+ obj:/lib/ld-2.3.6.so
+ obj:/lib/tls/i686/cmov/libdl-2.3.6.so
+ fun:dlopen
+}
+

ok, uploaded my approach after talking with jbailey. please reopen this bug when you really still have this problems and we can talk about your suppression rules again :)
Or do you have a testcase somewhere?

Sebastian's patch updates from the current 2.3.5 to 2.3.6 exceptions. This much is at least obviously correct. What problems does your patch solve that the others don't?

I'd be inclined to upload Sebastian's minimal fix and then try any failing tests you have.

Tks,
Jeff Bailey

Hi,
I have a test case, please note that my patch did include the fix for it.

Test case with my application
To retrieve you will need subversion.
To compile you will need libmysql dev.
cd /tmp
Proceed as follows:

svn checkout http://opensvn.csie.org/ptservices3
cd ptservices3
./configure --prefix=/tmp/ircsvs
make
make install
valgrind src/ircsvs

You should get the dlopen conditional warnings I have reported.

Thanks

This bug can be closed since it got a partial fix.
I have addressed remaining problem on bug #39491.

This was fixed already.

The suppression list needs to be updated for the current Gutsy /lib/ld-2.6.1.so. Currently the default suppressions lists seem to stop at glibc-2.5:

% ls /usr/lib/valgrind/*.supp

/usr/lib/valgrind/debian-libc6-dbg.supp /usr/lib/valgrind/glibc-2.4.supp
/usr/lib/valgrind/debian.supp /usr/lib/valgrind/glibc-2.5.supp
/usr/lib/valgrind/default.supp /usr/lib/valgrind/python.supp
/usr/lib/valgrind/glibc-2.2.supp /usr/lib/valgrind/xfree-3.supp
/usr/lib/valgrind/glibc-2.3.supp /usr/lib/valgrind/xfree-4.supp

So I still get valgrind warnings from /lib/ld-2.6.1.so.

% valgrind --version
valgrind-3.2.3-Debian

Ubuntu 7.10 current

cheers

Stephane