#include <unistd.h>
#include <stdio.h>
#include <string.h>
#include <errno.h>

int main(int argc, char** argv){
    execl("sadlfjsdf", "foo");
    printf("%s\n", strerror(errno));
}
[download]

If that says No such file or directory it's most likely a perl problem, and you should contact p5p. If it says Not a directory, it's most likely a Fedora problem (and I guess you should contact the Fedora developers).

BTW do you have a single dot in your $PATH? (Don't know if that makes a difference)

Tried the C code, it says "No such file or directory". p5p then?..

I don't have a single dot in my $PATH :

/usr/lib/qt-3.3/bin:/usr/kerberos/bin:/usr/lib/ccache:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/home/aharoni/bin

(/home/aharoni is my home dir.)

Tried the C code, it says "No such file or directory". p5p then?..

Yes, please. Usually they are very good with this kind of low-level stuff ;-)

Hm, that looks like a bad test to me.

$rc = system { "lskdfj" } "lskdfj";
unless( ok($rc == 255 << 8 or $rc == -1 or $rc == 256 or $rc == 512) )
+ {
     print "# \$rc == $rc\n";
}
 
unless ( ok( $! == 2  or  $! =~ /\bno\b.*\bfile/i or  
             $! == 13 or  $! =~ /permission denied/i or
             $! == 22 or  $! =~ /invalid argument/i  ) ) {
    printf "# \$! eq %d, '%s'\n", $!, $!;
}
[download]

By the time something gets around to checking $!, won't all of the system calls performed by ok() and print have set it to something else?

A good point, although it seems to work like this on my Fedora machine with this minimal program:

system { "lskdfj" } "lskdfj";
printf "# \$! eq %d, '%s'\n", $!, $!; # prints # $! eq 20, 'Not a dire
+ctory'
[download]

Another minor problem i can think of is the "random" command "lskdfj". It's paranoid thinking, but what if the user happens to have a file called /bin/lskdfj ? Maybe it should be checked with -e or something.

I'd bring it up on perl5-porters, but i am trying to subscribe and not receiving the confirmation email.