tags:

views:

6044

answers:

7

How do I run another program from within my C program, I need to be able to write data into STDIN of the programed launched (and maybe read from it's STDOUT)

Not sure if this is likley to be a standard C function, but I need the solution to work under Linux.

Thanks

Simon

+10  A: 

You want to use

popen
It gives you a unidirectional pipe with which you can access stdin and stdout of the program.

popen is standard on modern unix and unix-like OS, of which Linux is one :-)

Type

man popen

in a terminal to read more about it.

Cheers,
Steve

freespace
Note that it's stdin _or_ stdout, not both at once.
wnoise
In modern implementations, it is stdin AND stdout. The pipe is allowed to be bidirectional, though traditionally it is unidirectional.
freespace
A: 

I think you can use

freopen

for this .

Vhaerun
+3  A: 

Create two pipes with pipe(...), one for stdin, one for stdout.

fork(...) the process.

in the child process (the one where fork(...) returns 0) dup (...) the pipes to stdin/stdout.

exec[v][e] the to be started programm file in the child process.

In the parent process (the one where fork) returns the PID of the child) do a loop that reads from the child's stdout ( select(...) or poll(...), read(...) ) into a buffer, until the child terminates ( waitpid(...) ). Eventually supply the child with input on stdin if it expects some.

When done close(...) the pipes.

smink
A: 

You can use the system call, read manpage for system(3)

Jean Pierre Rupp
A: 

This is a duplicate of this question:

http://stackoverflow.com/questions/17140/how-do-you-spawn-another-process-in-c

Nathan Fellman
+3  A: 

I disagree with Nathan Fellman - the other question is not a duplicate of this, though the subject is related.

For simple unidirectional communication, popen() is a decent solution. It is no use for bi-directional communication, though.

IMO, imjorge (Jorge Ferreira) gave most of the answer (80%?) for bi-directional communication - but omitted a few key details.

  1. It is crucial that the parent process close the read end of the pipe that is used to send messages to the child process.
  2. It is crucial that the child process close the write end of the pipe that is used to send messages to the child process.
  3. It is crucial that the parent process close the write end of the pipe that is used to send messages to the parent process.
  4. It is crucial that the child process close the read end of the pipe that is used to send messages to the parent process.

If you do not close the unused ends of the pipes, you do not get sensible behaviour when one of the programs terminates; for example, the child might be reading from its standard input, but unless the write end of the pipe is closed in the child, it will never get EOF (zero bytes from read) because it still has the pipe open and the system thinks it might sometime get around to writing to that pipe, even though it is currently hung waiting for something to read from it.

The writing processes should consider whether to handle the SIGPIPE signal that is given when you write on a pipe where there is no reading process.

You have to be aware of pipe capacity (platform dependent, and might be as little as 4KB) and design the programs to avoid deadlock.

Jonathan Leffler
+2  A: 

I wrote some example C code for someone else a while back that shows how to do this. Here it is for you:

#include <sys/types.h>
#include <unistd.h>
#include <stdio.h>

void error(char *s);
char *data = "Some input data\n";

main()
{
  int in[2], out[2], n, pid;
  char buf[255];

  /* In a pipe, xx[0] is for reading, xx[1] is for writing */
  if (pipe(in) < 0) error("pipe in");
  if (pipe(out) < 0) error("pipe out");

  if ((pid=fork()) == 0) {
    /* This is the child process */

    /* Close stdin, stdout, stderr */
    close(0);
    close(1);
    close(2);
    /* make our pipes, our new stdin,stdout and stderr */
    dup2(in[0],0);
    dup2(out[1],1);
    dup2(out[1],2);

    /* Close the other ends of the pipes that the parent will use, because if
     * we leave these open in the child, the child/parent will not get an EOF
     * when the parent/child closes their end of the pipe.
     */
    close(in[1]);
    close(out[0]);

    /* Over-write the child process with the hexdump binary */
    execl("/usr/bin/hexdump", "hexdump", "-C", (char *)NULL);
    error("Could not exec hexdump");
  }

  printf("Spawned 'hexdump -C' as a child process at pid %d\n", pid);

  /* This is the parent process */
  /* Close the pipe ends that the child uses to read from / write to so
   * the when we close the others, an EOF will be transmitted properly.
   */
  close(in[0]);
  close(out[1]);

  printf("<- %s", data);
  /* Write some data to the childs input */
  write(in[1], data, strlen(data));

  /* Because of the small amount of data, the child may block unless we
   * close it's input stream. This sends an EOF to the child on it's
   * stdin.
   */
  close(in[1]);

  /* Read back any output */
  n = read(out[0], buf, 250);
  buf[n] = 0;
  printf("-> %s",buf);
  exit(0);
}

void error(char *s)
{
  perror(s);
  exit(1);
}
Steve Baker