I have Googled and searched Nabble, but to no avail have I found my answer.
I'm developing a daemon for use on Linux and I'm using Valgrind to make sure zero memory leaks occur. And so far so good. However, (or better known as the "but") I am running into the following message reported by Valgrind: invalid file descriptor 1019 in syscall socket( ) invalid file descriptor 1019 in syscall open( ) I have zero memory leaks, nadda, nothing. Some of the search hits relating to this error from others also pointed to other memory problem. But that is not the case here. Just my Valgrind log fills up with these two messages repeating as my daemon polls the ports in a non-blocking fashion. Once the executable stops Valgrind gives me my summary and I'm all clear memory wise. Not a single bit out of place. I found out the issue revolves around non-blocking socket calls only. If I make blocking socket calls this message does not appear. Once I tell my daemon to make non-blocking calls this message appears in the Valgrind log. My daemon functions properly either way, though it's better functionally as a non-blocking daemon to handle my pthreads. Any advice or any knowledge as to how to 1) resolve this so Valgrind doesn't see this as a reportable issue or 2) Valgrind ignores this trigger event. -- View this message in context: http://www.nabble.com/Valgrind-and-error-1019-tp20604591p20604591.html Sent from the Valgrind - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
