[Bug 53058] Incorrect socket reconnect behavior for DGRAM sockets

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=53058

--- Comment #3 from Peter <winebug at stather.me> ---
(In reply to Zeb Figura from comment #2)
> (In reply to Peter from comment #1)
> > Created attachment 72465 [details]
> > sock.c patch
> > 
> > This is a patch which fixes the issue as far as we can tell and there
> > *shouldn't* be any unintended side effects.
> 
> Hmm, I wonder if it's the right place to solve the problem, though. I wonder
> if we should never be setting DGRAM sockets to SOCK_CONNECTED state in the
> first place. There are only a few places where SOCK_CONNECTED is treated
> differently from SOCK_CONNECTIONLESS, but I dont think we have tests for
> whether any of those should apply to connectionless sockets.

I can't say I'm an expert on any of this, was just heavily involved in the
testing and debugging process for working out why our code doesn't work (a BF4
mod btw, which the regressing commit was meant to fix <_<).

It would make sense that a connectionless socket, which I think UDP DGRAM
sockets, are should be handled as such.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.