|
From: Tom H. <th...@cy...> - 2003-12-17 18:45:20
|
In message <200...@ac...>
Julian Seward <js...@ac...> wrote:
> 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)
> ==5883== by 0x3E1FD265: TEPty::commSetupDoneC() (in /opt/kde3/lib/kde3/
> libkonsolepart.so
> )
>
> running from fd=822 up to 1023. Sometimes it starts are 821 instead.
> Any ideas?
That's nothing to do with FV though is it? It looks more like something
that came from the syscall edits which cause FDs above about 822 to be
reserved for use by valgrind and that warning to be issued if the client
tries to do anything to them.
The problem is that some programs loop over all valid FDs and close
them when spawning a child or whatever, so you get that run of errors.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|