diff options
author | DJ Delorie <dj@redhat.com> | 2006-04-12 18:42:01 +0000 |
---|---|---|
committer | DJ Delorie <dj@redhat.com> | 2006-04-12 18:42:01 +0000 |
commit | 3db2e6ddf680eecc3060ba5a12d4c97072389d90 (patch) | |
tree | ab8a75ac527440e6f89d20b23afc619aa09d188c /include/libiberty.h | |
parent | 01d3a6ce134b69233591c6ad34ecdf844142e2c4 (diff) | |
download | gdb-3db2e6ddf680eecc3060ba5a12d4c97072389d90.zip gdb-3db2e6ddf680eecc3060ba5a12d4c97072389d90.tar.gz gdb-3db2e6ddf680eecc3060ba5a12d4c97072389d90.tar.bz2 |
merge from gcc
Diffstat (limited to 'include/libiberty.h')
-rw-r--r-- | include/libiberty.h | 41 |
1 files changed, 41 insertions, 0 deletions
diff --git a/include/libiberty.h b/include/libiberty.h index c264cb2..6bd318e 100644 --- a/include/libiberty.h +++ b/include/libiberty.h @@ -448,6 +448,47 @@ extern const char *pex_run (struct pex_obj *obj, int flags, const char *outname, const char *errname, int *err); +/* Return a `FILE' pointer FP for the standard input of the first + program in the pipeline; FP is opened for writing. You must have + passed `PEX_USE_PIPES' to the `pex_init' call that returned OBJ. + You must close FP yourself with `fclose' to indicate that the + pipeline's input is complete. + + The file descriptor underlying FP is marked not to be inherited by + child processes. + + This call is not supported on systems which do not support pipes; + it returns with an error. (We could implement it by writing a + temporary file, but then you would need to write all your data and + close FP before your first call to `pex_run' -- and that wouldn't + work on systems that do support pipes: the pipe would fill up, and + you would block. So there isn't any easy way to conceal the + differences between the two types of systems.) + + If you call both `pex_write_input' and `pex_read_output', be + careful to avoid deadlock. If the output pipe fills up, so that + each program in the pipeline is waiting for the next to read more + data, and you fill the input pipe by writing more data to FP, then + there is no way to make progress: the only process that could read + data from the output pipe is you, but you are blocked on the input + pipe. */ + +extern FILE *pex_write_input (struct pex_obj *obj, int binary); + +/* Return a stream for a temporary file to pass to the first program + in the pipeline as input. The file name is chosen as for pex_run. + pex_run closes the file automatically; don't close it yourself. */ + +extern FILE *pex_input_file (struct pex_obj *obj, int flags, + const char *in_name); + +/* Return a stream for a pipe connected to the standard input of the + first program in the pipeline. You must have passed + `PEX_USE_PIPES' to `pex_init'. Close the returned stream + yourself. */ + +extern FILE *pex_input_pipe (struct pex_obj *obj, int binary); + /* Read the standard output of the last program to be executed. pex_run can not be called after this. BINARY should be non-zero if the file should be opened in binary mode; this is ignored on Unix. |