Hi all,
I am having an immensely weird problem with newest lazarus (which was definitely not there before). The problem affects only code that makes use of tprocess to get output from a shell-script and feed it back as a function result. It is triggered whenever stdout of the main program is piped. Whether to a file with > or to a program with | For some reason the output from tprocess is suddenly all messed up and ends up being random lines from my program's output.

This is rather disturbing as I have a large amount of debug info which gets constantly dumped to stdout to allow me to track the process of the program and identify problems with the implementation as it runs. But, should I try to log this data with a pipe, or to seek out a specific fragment with grep, suddenly the tprocess function gets completely confused and I end up with random strings from my own output dumped where the output of a shell-script is meant to be.

What could cause this ? A stack overflow in the tprocess ? Any idea where I should look ? Was something in tprocess changed recently ?

My tprocess code is almost exactly based on the examples in the tutorial on the lazarus wiki.

A.J.
--
"Any sufficiently advanced technology is indistinguishable from magic" - Clarke's law "Any technology that is distinguishable from magic is insufficiently advanced" -Gehm's corollary "Any technologist that is distinguishable from a magician is insufficiently advanced" - My corollary
The worlds worst webcomic: http://silentcoder.co.za/scartoonz
The worlds best cybercafe manager: http://outkafe.outkastsolutions.co.za

begin:vcard
fn:AJ Venter
n:Venter;AJ
org:Global Pact Trading Pty. Ltd.;OutKast Solutions
email;internet:[EMAIL PROTECTED]
title:Director of Product Development
tel;work:+27 21 554 5059
tel;fax:+27 11 252 9197
tel;cell:+27 83 455 9978
url:http://www.outkastsolutions.co.za
version:2.1
end:vcard

Reply via email to