>> Any
>> > help to solve this would be useful.
>> >
>> > Thanks.
>> >
>> > Venki
>> >
>> >
>>
>> -----
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>&g
ee the 'segmentation fault' message in the stream output.
>> Any
>> help to solve this would be useful.
>>
>> Thanks.
>>
>> Venki
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail:
On 9/13/07, Bruce Atherton <[EMAIL PROTECTED]> wrote:
> It is entirely possible that the output never reaches Ant. The standard
> C library is typically set up to buffer data on the standard file
> handles, for efficiency purposes.
>
> To get around this, you could:
>
> 1) do a flush() on the std
It is entirely possible that the output never reaches Ant. The standard
C library is typically set up to buffer data on the standard file
handles, for efficiency purposes.
To get around this, you could:
1) do a flush() on the stdout and stderr streams before the
segmentation fault (assuming
venki wrote:
Hi,
I am using org.apache.tools.ant.taskdefs.Execute combined with
org.apache.tools.ant.taskdefs.PumpStreamHandler to execute an external C
program. When the external C program segfaults, I am not able to to see any
output that came from the external C program before it segfaults. Al
able to see the 'segmentation fault' message in the stream output. Any
help to solve this would be useful.
Thanks.
Venki
--
View this message in context:
http://www.nabble.com/org.apache.tools.ant.taskdefs.Execute-and-segafult-tf4431366.html#a12641861
Sent from the Ant - Users ma
