Valgrind Invalid File Descriptor In Syscall Close
Valgrind shows me the following: 13880 Warning: invalid file descriptor -1 in syscall close Is there an easy way to investigate this error? I mean - to show stack-trace for example? It's a huge project, I can't manually check each close. Also, I guess this would be the same for each sys call on bad filed descriptor.
[Valgrind-users] invalid file descriptor -1 in syscall close() Re: [Valgrind-users] invalid file. Invalid file descriptor -1 in syscall close().
I run it like: valgrind -trace-children=yes -track-fds=yes -log-fd=2 -error-limit=no -leak-check=full -show-possibly-lost=yes -track-origins=yes -show-reachable=yes./exe the exe is with debug information. A bigger piece of the valgrind's output is: 13880 Conditional jump or move depends on uninitialised value(s) 13880 at 0x5A4022F:??? (in /lib/i686/cmov/libc-2.11.3.so) 13880 by 0x5A57323:??? (in /lib/i686/cmov/libc-2.11.3.so) 13880 by 0x5A56EC2:??? (in /lib/i686/cmov/libc-2.11.3.so) 13880 by 0x5A5555B: localtimer (in /lib/i686/cmov/libc-2.11.3.so) 13880 by 0x754E983:???
Invalid File Descriptor To Icu Data Received
10 Dec 2010 12:27 Alexander Nozdrin Description: main.kill started to fail sporadically under valgrind with the following warning: invalid file descriptor -1 in syscall close The failure was noticed on Nov-27 in daily-trunk-bugfixing The symptoms are similar to. However was about replication, and was closed by adding a suppression for that warning. That warning can be seen in rplheartbeatbasic, but it is 'Ok' there and can be ignored (by valgrind suppression added by ). That story is discussed in. How to repeat: Check out PB.