Description of problem: Valgrind reports this: ==26071== Warning: invalid file descriptor -100 in syscall openat() ==26071== at 0x3E17B6: __openat64_nocancel (openat.c:95) ==26071== by 0x3E18EC: openat64 (openat.c:164) ==26071== by 0x804B242: rpl_getcwd (getcwd.c:218) ==26071== by 0x804AD1A: xgetcwd (xgetcwd.c:39) ==26071== by 0x804925A: main (pwd.c:322) --26071-- Caught __NR_exit; running __libc_freeres() --26071-- REDIR: 0x3914A0 (memset) redirected to 0x4006580 (memset) When running evolution. Could be that this is just a matter of teaching valgrind about the special case of using -100 as a file descriptor in the openat case? Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
No idea. Jakub?
Anyone know how to reproduce this?
'valgrind -v -v --leak-check=full --num-callers=30 pwd' will do it here at least.
I can't reproduce this. Does it still happen? Changing component to valgrind since that's most likely where the problem is/was.
* Tue Sep 26 2006 Jakub Jelinek <jakub> 3.2.1-2 - fix openat handling (#208097)