[Qt-interest] Does QProcess::readAllStandardOutput have a limit?
Eric Clark
eclark at ara.com
Thu Dec 2 20:16:43 CET 2010
> -----Original Message-----
> From: qt-interest-bounces at trolltech.com [mailto:qt-interest-
> bounces at trolltech.com] On Behalf Of Thiago Macieira
> Sent: Thursday, December 02, 2010 1:01 PM
> To: qt-interest at trolltech.com
> Subject: Re: [Qt-interest] Does QProcess::readAllStandardOutput have a
> limit?
>
> Em Quinta-feira, 2 de Dezembro de 2010, às 19:31:28, Eric Clark escreveu:
> > I was wondering if anyone knew of some sort of limitation on the
> > number of bytes that readAll, readAllStandardOutput, or
> > setStandardOutputFile will read from the process? In all cases, the
> > text is cutoff at the same point in the output. I do not see anywhere
> > in the documentation for QProcess where it says there is a limit, but
> > the results I am getting leads me to believe that there is a limit.
>
> The limit probably comes from the Operating System's pipe buffer limits and
> scheduling. It's not a hard limit, it just happens that your process was woken
> up when the data wasn't complete.
>
> You should receive the rest of the data soon.
What do you mean by soon? I am not receiving any more calls to my slot connected to the readyReadStandardOutput signal. The process that is running outputs a bunch of startup text and then goes into an infinite loop waiting to receive commands. I have waited a while (minutes) after the process was started and I do not receive any more signals that the standard output is ready to be read.
Thanks,
Eric
> --
> Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
> Senior Product Manager - Nokia, Qt Development Frameworks
> PGP/GPG: 0x6EF45358; fingerprint:
> E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
More information about the Qt-interest-old
mailing list