On 07/16/2012 02:14 PM, daniel.janzon wrote: > Hi guys, > > I get a lot of > > ==8186== Warning: invalid file descriptor 1019 in syscall open() >
That message is issued if the file descriptor exceeds the limit that is allowed for the process. On my Ubuntu 12.something uname -a tells me I can use 1024 file descriptors. Valgrind reserves 10 for itself. So 1019 would be off limits on my system. If this applies to you: increase the limit, does it help? If not: Run valgrind with --trace-children=yes --trace-syscalls=yes --track-ids=yes That should shed some light. Search for sys_open (or similar) and look at the next line. It contains the file descriptor in *hex*. If that invalid file descriptor does not show up, then I'm afraid only a gdb session on valgrind will help. Florian ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
