Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#15081 closed bug (fixed)

listen() causes a socket to be "connected"

Reported by: leorize Owned by: axeld
Priority: normal Milestone: R1/beta2
Component: Network & Internet/TCP Version: R1/Development
Keywords: Cc:
Blocked By: Blocking: #2967
Platform: All

Description

Calling listen() will assign a 0.0.0.0 peer to the socket, where as no connection has been accepted yet.

The demo below will describe the problem. To run: 

$ gcc -o peerless -lnetwork peerless.c
$ ./peerless

Expected result:

Exit code 0, no output

Got: 

Expected ENOTCONN, got 0

Attachments (1)

peerless.c​ (767 bytes ) - added by leorize 5 years ago.

Download all attachments as: .zip

Change History (10)

by leorize, 5 years ago

Attachment: peerless.c​ added

comment:1 by korli, 5 years ago

Is it really different from #2967?

comment:2 by leorize, 5 years ago

Is it really different from #2967?

Yea, that bug revolves around connect().

comment:3 by waddlesplash, 5 years ago

Resolution: → fixed
Status: new → closed

Fix merged in hrev54099.

comment:4 by waddlesplash, 5 years ago

Resolution: fixed
Status: closed → reopened

Reverted due to Qt breakage.

comment:5 by waddlesplash, 5 years ago

Blocked By: 2967 added

comment:7 by korli, 5 years ago

Fix merged again in hrev54132. Tested with UDP and TCP.

comment:8 by waddlesplash, 5 years ago

Blocked By: 2967 removed
Blocking: 2967 added
Resolution: → fixed
Status: reopened → closed

comment:9 by nielx, 5 years ago

Milestone: Unscheduled → R1/beta2

Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone

Note: See TracTickets for help on using tickets.