[Qt-interest] Major bug inQAbstractSocket'smethodwaitForReadyRead()

[Srdjan Todorovic]

Hi,

On 25/06/2009, Patric <userqt at gmail.com> wrote:
>>1. My network cable is plugged in. The first setRequest is successful, so
>>it returns true. After that I'm removing the cable. The second request is
>>unsuccessful, so it waits 5 seconds. And all other requests wait for >five
>>seconds. And this is the correct behaviour.
>
>
>
>>2. My cable IS NOT plugged. The first setRequest is unsuccessful, so it
>>waits 5 seconds and continues with the second. But here ! it don't wait 5
>>seconds, it immediately returns FALSE. Which I think is not >correct.
>
> These are the tests. I'm using a network module (hardware device) here which
> I control via SNMP.

Those are not tests. These are descriptions of your problem.

>I can't write a small program, because it'll not be so
> small and it'll not work without the device.

In which case, maybe your device has a bug ;)

Are you saying that you cannot create two simple programs and have
each on two machines?

Not even a hello-echo program?

> But I'm using the method through the QUdpSocket class.
> I'm just saying it's possible this method to have a bug with randam
> occurance. I can't define what's the reason for it.

Again, read below:

>> Do you have source code for a small, simple program that you can send
>> us, that does not do anything SNMP, and that still has this problem?
>>
>> Basically, you say there's a bug, we say "prove it!" :)

Srdjan