root@test3:/home/foo # valgrind ./foo ==92585== Memcheck, a memory error detector ==92585== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al. ==92585== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info ==92585== Command: ./blockd -i igb4,igb5 -I igb1 -Q 8 -e 8 -E 8 -F /dev/null ==92585== ==92585== Warning: invalid file descriptor -100 in syscall openat() ==92585== Warning: invalid file descriptor -100 in syscall openat() Cannot open "/usr/local/lib/valgrind/vgpreload_core-amd64-freebsd.so" ==92585== ==92585== HEAP SUMMARY: ==92585== in use at exit: 0 bytes in 0 blocks ==92585== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==92585== ==92585== All heap blocks were freed -- no leaks are possible ==92585== ==92585== For counts of detected and suppressed errors, rerun with: -v ==92585== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) .. this was fixed by stas in his valgrind port to freebsd, but we still don't have an updated binary package with a working valgrind. Can this please be fixed? This is really frustrating.
Fix Summary.
Adrian, Was this fixed a while ago in r379696? https://svnweb.freebsd.org/ports?view=revision&revision=379696 The 963c4a7 commit hash mentions in the log the "fix openat() wrapper" https://bitbucket.org/stass/valgrind-freebsd/commits/963c4a777573b5fb1ebaefbc7daf2bc38dbefa6f
Adrian, I think we came to the conclusion that with Valgrind 3.10.0 in ports now that this is ready to be closed.