in reply to mysterious error of read function in solaris

You're dying whenever $! is a non-false value. But $! having a non-false value is not an indication anything is wrong. Check the system call, only if that is false, $! will have a useful value. In all other cases, you may not rely on $! having a sensible value.

In this, my bet is that Solaris sets errno to 13 during one of the system calls that are being made. And an OS is free to do so, the 13 only needs to signal something if the call fails (which it won't, because if the read fails, you aren't testing $!).

Replies are listed 'Best First'.
Re^2: mysterious error of read function in solaris
by david2008 (Scribe) on Jan 19, 2012 at 15:39 UTC
    Which variable should i check if read fails?
      Whatever variable you put the return value of read in. From perldoc -f read
      Returns the number of characters actually read, 0 at end of file, or undef if there was an error (in the latter case $! is also set).
      So, you'd do something like:
      my $r; while ($r = read ...) { ... do stuff here ... } die "read failed: $!" unless defined $r;
      I guess since 5.10, you could also write:
      while (read(...) // die "read failed: $!") { ... do stuff here ... }
      but I don't think I would want to recommend that.