[Gambas-user] Issue 435 in gambas: Socket blocks events, timeout not used

[gambas at ...2524...]

Status: New
Owner: ----
Labels: Version Type-Bug Priority-Medium OpSys-Any Dist-Any Arch-Any  
Desktop-Any GUI-Any

New issue 435 by r... at ...1740...: Socket blocks events, timeout not used
http://code.google.com/p/gambas/issues/detail?id=435

1) Describe the problem.

Start Gambas3 ClientSocket example, and for host fill in an non-existing IP  
address, for example a private address from a range outside your own.
For example 192.168.171.1

Bug #1:
It's status stays on 'Looking up hostname' but it's past that part already.

The app does a request in syn_sent state, but doesn't get a SYN_SENT back  
because the IP isn't reachable.
$ netstat -an|grep 32340
tcp        0      1 192.168.178.80:50911    192.168.171.1:32340     SYN_SENT
This is ok but then you have:

Bug #2:
The app freezes / socket works in non-async mode, stops and blocking all  
events (in my application this was what I saw...)

Bug #3:
And doesn't time out after the (default?) timeout of 10 sec, but after a  
minute or longer.. Even if you specify a shorter .Timeout, it doesn't use  
it.

If you try this with Gambas2 ClientSocket example you see correctly 'Host  
Found. Connecting'...

It times out after the (default?) of 10 seconds.

And doesn't block the program, did try this with the ClientSocket example,  
but I know this from my own project.

2) GIVE THE FOLLOWING INFORMATIONS (if they are appropriate):

Version: TRUNK
Revision: r5686
[System]
OperatingSystem=Linux
Kernel=3.8.0-22-generic
Architecture=x86_64
Distribution=Ubuntu 13.04
Desktop=GNOME
Theme=QGtk
Language=en_US.UTF-8
Memory=7954M

[Libraries]
Curl=libcurl.so.4.3.0
GStreamer=libgstreamer-0.10.so.0.30.0
GTK+=libgtk-x11-2.0.so.0.2400.17
Qt4=libQtCore.so.4.8.4
SDL=libSDL-1.2.so.0.11.4
Poppler=libpoppler.so.28.0.0

3) Provide a little project that reproduces the bug or the crash.
See ClientSocket example.

4) If your project needs a database, try to provide it, or part of it.
NA

5) Explain clearly how to reproduce the bug or the crash.
See above

6) By doing that carefully, you have done 50% of the bug fix job!

IMPORTANT NOTE: if you encounter several different problems or bugs, (for
example, a bug in your project, and an interpreter crash while debugging
it), please create distinct issues!

-- 
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings