Re: [Valgrind-users] invalid file descriptor in syscall close()

2011-08-23 Thread Mahmood Naderan
>Give the invalid file descriptor (ie you're trying to close a descriptor >that doesn't represent an open file) and the attempt to access inaccessible >memory inside fclose I'm guessing you passed it a dodgy pointer. You are right. Using verbose mode, it shows a failure in open file. ==4513

Re: [Valgrind-users] invalid file descriptor in syscall close()

2011-08-23 Thread Tom Hughes
On 23/08/11 16:10, Mahmood Naderan wrote: > Hi > Using valgrind to detect the problem, I see many messages like this: > > ==4513== Warning: invalid file descriptor 4546 in syscall close() > ==4513== Warning: invalid file descriptor 4567 in syscall close() > ==4513== Warning: invalid file descriptor

[Valgrind-users] invalid file descriptor in syscall close()

2011-08-23 Thread Mahmood Naderan
Hi Using valgrind to detect the problem, I see many messages like this: ==4513== Warning: invalid file descriptor 4546 in syscall close() ==4513== Warning: invalid file descriptor 4567 in syscall close() ==4513== Warning: invalid file descriptor 4567 in syscall close() ==4513== Warning: invalid fi