https://bugs.winehq.org/show_bug.cgi?id=38665 --- Comment #10 from Bruno Jesus <00cpxxx(a)gmail.com> --- (In reply to Austin English from comment #9)
Thanks. This looks a bit suspicious: fixme:winsock:convert_socktype_u2w unhandled UNIX socket type 5 fixme:winsock:convert_proto_u2w unhandled UNIX socket protocol 132 fixme:winsock:convert_socktype_u2w unhandled UNIX socket type 5 fixme:winsock:convert_proto_u2w unhandled UNIX socket protocol 132 fixme:winsock:convert_socktype_u2w unhandled UNIX socket type 5 fixme:winsock:convert_proto_u2w unhandled UNIX socket protocol 132 fixme:winsock:convert_socktype_u2w unhandled UNIX socket type 5 fixme:winsock:convert_proto_u2w unhandled UNIX socket protocol 132
cc'ing Bruno.
I don't expect any sane application to bail out when a SOCK_SEQPACKET does not work. I'll try the app when I have more time. -- 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.