CODEWITHSUNDEEP
c++shellsystem
Pijusn
Pijusn

Reputation: 11293

C++: system(0) Returns 0

When I call system(0) it returns 0, which means shell is not available.

When a command using system (calls gcc to compile a hello world program), it works just fine but returns -1 (I assume it's the same cause as for system(0) returning 0). What causes it to be "not available" and why does it work anyway?

Compiler: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3)

OS: Ubuntu 11.10

EDIT

Errno says No Child Processes.

I have also compiled another test program that does not do anything but calls system(0) and it returns nonzero value. Can it be affected by Code::Blocks?

EDIT

So far I have figured out that system(0) only fails after I start my first pthread.

SOLVED

I used fork in my early implementation of one of this piece of code:

signal(SIGCHLD,SIG_IGN);

I used it to "handle" zombies. I just found out that this caused the error.

Upvotes: 3

Views: 4106

Answers (2)

Sander De Dycker
Sander De Dycker

Reputation: 16243

This could happen if you are ignoring the SIGCHLD signal using code like :

signal(SIGCHLD, SIG_IGN);

This would cause system to return -1 when all children have ended, setting errno to ECHILD.

Refer to http://pubs.opengroup.org/onlinepubs/009695399/functions/wait.html. Specifically :

If the calling process has SA_NOCLDWAIT set or has SIGCHLD set to SIG_IGN, and the process has no unwaited-for children that were transformed into zombie processes, the calling thread shall block until all of the children of the process containing the calling thread terminate, and wait() and waitpid() shall fail and set errno to [ECHILD].

Upvotes: 3

Tio Pepe
Tio Pepe

Reputation: 3089

Man says:

The value returned is -1 on error (e.g. fork(2) failed), and the return status of the command otherwise. This latter return status is in the format specified in wait(2). Thus, the exit code of the command will be WEXITSTATUS(status). In case /bin/sh could not be executed, the exit status will be that of a command that does exit(127). If the value of command is NULL, system() returns nonzero if the shell is available, and zero if not.

If you have no sh in your path or is not an executable is not available. Check your configuration.

If system returns -1 may be a problem executing fork, so check errno variable value or maybe the return status of the invoked command, that may be also -1. Verify exit status of your command executed from chell.

Upvotes: 1

Related Questions