commit | e4a905f384b8d1ab9b916174b2a0b0d9ddf71614 | [log] [tgz] |
---|---|---|
author | mjw <mjw@a5019735-40e9-0310-863c-91ae7b9d1cf9> | Tue Feb 10 13:39:04 2015 +0000 |
committer | mjw <mjw@a5019735-40e9-0310-863c-91ae7b9d1cf9> | Tue Feb 10 13:39:04 2015 +0000 |
tree | cff9aeb67ed9a0bbb41d75443db19fa9c930d419 | |
parent | 237fd431ca0261d28ee5dec6d005af237002d0e0 [diff] |
Bug #344007 accept4 syscall unhandled on arm64 (242) and ppc64 (344) ppc64 might fall back to socketcall in some cases, but arm64 always uses accept4 syscall directly. Some (confusing) background on when/how glibc (wrongly) decides to use a direct accept4 or the socketcall system call: https://sourceware.org/ml/libc-alpha/2013-12/msg00014.html git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14926 a5019735-40e9-0310-863c-91ae7b9d1cf9