linuxdcpp-team team mailing list archive
-
linuxdcpp-team team
-
Mailing list archive
-
Message #01275
[Bug 590359] [NEW] Socket::resolve isn't thread safe
Public bug reported:
gethostbyname() shouldn't be called from multiple threads in Linux. As
it may return pointer to static data that will be overwritten by the
next call. (And based on the few stacktraces I've seen lately it is
overwritten.) Windows seems to allocate the data for gethostbyname from
thread local storage, so that will probably explain why it took so long
to be reported.
** Affects: dcplusplus
Importance: Undecided
Status: New
** Affects: linuxdcpp
Importance: Medium
Assignee: Razzloss (razzloss)
Status: Confirmed
** Tags: core crash
** Also affects: dcplusplus
Importance: Undecided
Status: New
--
Socket::resolve isn't thread safe
https://bugs.launchpad.net/bugs/590359
You received this bug notification because you are a member of LinuxDC++
Team, which is subscribed to LinuxDC++.
Status in DC++: New
Status in Linux DC++: Confirmed
Bug description:
gethostbyname() shouldn't be called from multiple threads in Linux. As it may return pointer to static data that will be overwritten by the next call. (And based on the few stacktraces I've seen lately it is overwritten.) Windows seems to allocate the data for gethostbyname from thread local storage, so that will probably explain why it took so long to be reported.
Follow ups
-
[Bug 590359] Re: Socket::resolve isn't thread safe
From: Steven Sheehy, 2011-04-17
-
[Bug 590359] Re: Socket::resolve isn't thread safe
From: poy, 2010-07-05
-
[Bug 590359] Re: Socket::resolve isn't thread safe
From: Razzloss, 2010-06-06
-
[Bug 590359] Re: Socket::resolve isn't thread safe
From: Launchpad Bug Tracker, 2010-06-06
-
[Bug 590359] Re: Socket::resolve isn't thread safe
From: Razzloss, 2010-06-06
-
[Bug 590359] Re: Socket::resolve isn't thread safe
From: Razzloss, 2010-06-06
-
[Bug 590359] Re: Socket::resolve isn't thread safe
From: poy, 2010-06-06
-
[Bug 590359] Re: Socket::resolve isn't thread safe
From: Launchpad Bug Tracker, 2010-06-06
-
[Bug 590359] Re: Socket::resolve isn't thread safe
From: Toast, 2010-06-06
-
[Bug 590359] Re: Socket::resolve isn't thread safe
From: Razzloss, 2010-06-06
-
[Bug 590359] [NEW] Socket::resolve isn't thread safe
From: Razzloss, 2010-06-06
References