Hi Jeff,
On Tuesday 25 August 2009 17:09:14 Jeff Hill wrote:
> After further testing on newer linux versions where the debugger seems to
> actually function correctly I now strongly suspect that this issue is
> caused by this change. The symptom is that two threads that CA creates to
> manage TCP circuits never shutdown. They need to shutdown typically when
> the TCP circuit disconnects or when the last channel on the circuit is
> deleted. The bug was introduced in R3.14.9. See mantis 363.
Can you write a version of blockingSockTest that demonstrates this and
correctly responds with socketSigAlarmRequired? Unfortunately you'll have to
test it against R3.14.9 or R3.14.10 — I eviscerated the sigAlarm routines for
this release since our use of this signal broke the posix timer library
(which relies on SIG_ALARM) that some external libraries use. We'll have to
switch to using a different signal if we're going to bring it back (we
probably should make the signal number we use configurable).
- Andrew
--
The best FOSS code is written to be read by other humans -- Harold Welte
- Replies:
- RE: proper thread cleanup on Linux? Jeff Hill
- References:
- proper thread cleanup on Linux? Jeff Hill
- RE: proper thread cleanup on Linux? Jeff Hill
- Navigate by Date:
- Prev:
RE: proper thread cleanup on Linux? Jeff Hill
- Next:
RE: proper thread cleanup on Linux? Jeff Hill
- Index:
2002
2003
2004
2005
2006
2007
2008
<2009>
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: proper thread cleanup on Linux? Jeff Hill
- Next:
RE: proper thread cleanup on Linux? Jeff Hill
- Index:
2002
2003
2004
2005
2006
2007
2008
<2009>
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|