[prev in list] [next in list] [prev in thread] [next in thread]
List: pidgin-tracker
Subject: Re: [Pidgin] #17123: "getsockname: Windows socket error #10014" during file transfer
From: "Pidgin" <trac () pidgin ! im>
Date: 2018-02-11 11:14:00
Message-ID: 062.49b52ab6081889ba27855a889d68e9b9 () pidgin ! im
[Download RAW message or body]
#17123: "getsockname: Windows socket error #10014" during file transfer
-------------------------------------------------+-------------------------
Reporter: martin.von.wittich | Owner:
Type: defect | Status: new
Milestone: | Component: libpurple
Version: 2.11.0 | Resolution:
Keywords: filetransfer winsock port |
getsockname |
-------------------------------------------------+-------------------------
Comment (by stefanb):
This probably has the same root cause as #17156. Please see my suggested
fix for `purple_network_get_port_from_fd()`. That solution should apply
for all places in libpurple code that uses `getsockname()`,
`gethostbyname()` and friends.
--
Ticket URL: <https://developer.pidgin.im/ticket/17123#comment:3>
Pidgin <https://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@pidgin.im
https://pidgin.im/cgi-bin/mailman/listinfo/tracker
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic