Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

Should look at C

by petr999 (Acolyte)
on Jan 20, 2010 at 12:04 UTC ( [id://818433]=note: print w/replies, xml ) Need Help??

in reply to native exit codes 512 and 2304

Seem as got it: I should look at C code for particular numbers.
But it should be nice to have typical exit codes and their probable explanations as a document to read or look up.

Replies are listed 'Best First'.
Re: Should look at C
by cdarke (Prior) on Jan 20, 2010 at 13:28 UTC
    Here's a quick and dirty way of translating exit codes to their C error strings:
    local $! = 512 >> 8; print "$!\n";
    BUT you should be careful! Not everyone uses the C runtime-library error numbers. Exit codes are application specific, they should be listed in the application documentation.
Re: Should look at C
by Corion (Patriarch) on Jan 20, 2010 at 12:08 UTC

    Your OS should have these. They are specific to each OS.

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://818433]
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others examining the Monastery: (5)
As of 2024-06-15 00:50 GMT
Find Nodes?
    Voting Booth?

    No recent polls found

    erzuuli‥ 🛈The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.