|
From: Jeremy F. <je...@go...> - 2003-12-18 01:09:50
|
On Wed, 2003-12-17 at 11:49, Julian Seward wrote: > I'm experiencing some turbulence on SuSE 9. > > Running any program on memcheck, there are a lot more uninit-val > errors reported than before. Even with 'ls'. Are the early? Are they in ld-linux.so? Are they str*() functions? > Probably easier to track down, when running /opt/kde3/bin/kate on memcheck, > there are also hundreds of messages like this: > > ==5883== Warning: invalid file descriptor 822 in syscall close() > ==5883== at 0x3D505D71: close (in /lib/libc.so.6) > ==5883== by 0x3E1FCB68: TEPty::startPgm(char const*, QValueList<QCString>&, > char const*) > (in /opt/kde3/lib/kde3/libkonsolepart.so) [...] > running from fd=822 up to 1023. Sometimes it starts are 821 instead. > Any ideas? As Tom said, this should occur in 2.1.0 as well - that's part of the syscalls changes. Maybe the trick would be to change the client's view of the soft (or hard) file-descriptor limit, in case they use that to work out what file-descriptors to close. Anyway, it's basically noise - maybe I shouldn't bother warning about those... J |