[Qt-interest] QNetworkAccessManager and SIGPIPE

[Jason Wood]

There's no calls to signal() in the code which is what would remove the
handler right?

I think the problem may be related to a throttling method I'm using which I
found on the mailing list somewhere. It involved a subclassed QIODevice
throttling the data via the readData() function which I think is interfering
with the abort somewhere as the request is aborted as normal when the
throttling is not present. Is this a recommended way to throttle uploading
data or is there a better way?

Thanks,
Jason.

On Mon, Feb 22, 2010 at 5:59 PM, Thiago Macieira <thiago at kde.org> wrote:
>
>> Em Segunda-feira 22 Fevereiro 2010, às 18:20:58, você escreveu:
>> > Looking deeper into the logs on the server, I see that the server also
>> has
>> > a "Broken pipe" error at the time of the SIGPIPE in the application. It
>> > seems the SIGPIPE should be caught by the QNetworkAccessManager and
>> > returned as a connection error? This doesn't seem to be the case as the
>> > connections sit idle after the error without ever returning.
>>
>> Qt installs a signal handler for SIGPIPE.
>>
>> Does your application accidentally remove such a signal?
>>
>> --
>> 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
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20100222/07869317/attachment.html