[ros-bugs] [Bug 777] New: concurrent socket() calls return same descriptor in at least r17848

[ReactOS.Bugzilla at reactos.com]

http://reactos.com/bugzilla/show_bug.cgi?id=777

           Summary: concurrent socket() calls return same descriptor in at
                    least r17848
           Product: ReactOS
           Version: TRUNK
          Platform: VMWare 5
               URL: http://waxdragon.homeip.net/~ford/wssample.rar
        OS/Version: ReactOS
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Networking
        AssignedTo: ros-bugs at reactos.com
        ReportedBy: waxdragon at gmail.com


I'm pretty sure this bug has been here a long time.  Running two copies of
SIMPLT32.exe from the winsock sample archive (linked) under r17848, After
choosing  "Connect" and providing an address of a echo server (ASECHO32 in same
package if you need one), the ConnectTCP() call returns the same number. 
Looking at the sample source, ConnectTCP() is a wrapper to socket(), so our
socket it returning the same descriptor for both calls.  If you choose "Start
Sending" in either connected client, the connection will hang after sending 2048
bytes.  The echo client runs rather well if you run only one. ;0)

Something interesting I noticed, even though they both had the same descriptor,
the echo server registered two connections, and if you don't try to send any
data, instead just closing the connections, they will close gracefully.

-- 
Configure bugmail: http://reactos.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.