Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

Re^3: System call + signals = bad return code?

by bluto (Curate)
on Sep 28, 2007 at 23:00 UTC ( #641635=note: print w/ replies, xml ) Need Help??

in reply to Re^2: System call + signals = bad return code?
in thread System call + signals = bad return code?

I was confused by your example. Sorry. This statement though still holds: I've seen similar cases where system returns an invalid result if I've already forked off an unrelated process and it happens to die when system() is executing. (i.e. in addition to signals, process reaping is problematic). You may want to try replacing system() with fork/exec/waitpid. The waitpid will return the status for the child pid you pass to it.

Comment on Re^3: System call + signals = bad return code?

Log In?

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

How do I use this? | Other CB clients
Other Users?
Others browsing the Monastery: (6)
As of 2015-11-28 15:02 GMT
Find Nodes?
    Voting Booth?

    What would be the most significant thing to happen if a rope (or wire) tied the Earth and the Moon together?

    Results (743 votes), past polls