Comment 13 for bug 1577926

What I think that might be useful is being able to get a list of open file descriptors of the process and the point of the execve is being called. I suspect that its failing because it doesn't have access to something so it get an EPERM

The only reference to execve failing in the man page is because of setuid and a file system being mounted nosuid

Unless somebody wants to read the kernel code and figure out why execve can return EPERM