ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: create cab in linux; patch request
Date Thu, 17 Oct 2002 12:47:39 GMT
On Mon, 14 Oct 2002, <> wrote:

>>>Hmm, but if you read from stdin, you'll block until something is
>>>available to read, so this shouldn't be a problem, right?


this here (from the javadocs of java.lang.Process)

| The created subprocess does not have its own terminal or console. All
| its standard io (i.e. stdin, stdout, stderr) operations will be
| redirected to the parent process through three streams
| (Process.getOutputStream(), Process.getInputStream(),
| Process.getErrorStream()). The parent process uses these streams to
| feed input to and get output from the subprocess. Because some native
| platforms only provide limited buffer size for standard input and
| output streams, failure to promptly write the input stream or read the
| output stream of the subprocess may cause the subprocess to block, and
| even deadlock.

is the stuff that worries me (and that your patch may or may not
trigger).  The current code seems to run into the "failure to promptly
read the output stream" on your setup, I don't want to replace it with
code that runs into the other case in other environments.

> With all due respect, I don't see what all the fuss is about.

"all this fuss" is about a committer who remembers he applied a patch
to a while ago and worked with the one who submitted the
patch because an initial version had problems with the stuff above.

I can't test the task myself, neither can any other committer (it
seems), so I prefer to at least be comfortable with what I commit, and
this may involve some discussion.

> At any rate, I've submitted a bug report to the apache bug database
> which fixes the problem, works for me, and should reasonably work
> for others.

Thank you


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message