Thank you for the advice. What I see in an open file descriptor to my valgrind.log file. The only thing that holds that fd is valgrind. At least I see it's not my issue. Once I remove the argument --log-file= the error no longer shows up when Valgrind gives it's summary. So from my point of view, this is ok.
The 3 (out for 4) remaining open fds is to /dev/pts/0. So I'm not sure who or what is trying to display to a pseudo terminal. My code only interfaces with syslog. I appreciate your advice. I'm just glad not to see anything on my end. Julian Seward-2 wrote: > > >> invalid file descriptor 1019 in syscall socket( ) >> invalid file descriptor 1019 in syscall open( ) > > You sure you haven't got a file descriptor leak? What > happens if you rerun with --track-fds=yes? > > -- View this message in context: http://www.nabble.com/Valgrind-and-error-1019-tp20604591p20674913.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
