[Quickfix-developers] ThreadedSocketAcceptor Segmentation Faults

[Guillermo A. A. <gar...@vi...>]

Hi all,

Since I upgraded to Quickfix 1.10.2 (prior we were using 1.9.4) i'm =
getting
a random segmentation fault when sessions log off. I couldn't find a =
pattern
to reproduce it, or even a "more probable" scenario, it just happens =
from
time to time.

Before entering a bug report, i'd like to know if someone has faced this =
(or
similar) problem, or if someone thinks the problem is on my side.

All the dumped cores from this segmentation fault read the same:

#0  0x00cb8b60 in pthread_detach () from /lib/tls/libpthread.so.0
#1  0x00870b97 in FIX::thread_detach (thread=3D0) at Utility.cpp:344
#2  0x0081d4c8 in FIX::ThreadedSocketAcceptor::removeThread =
(this=3D0x8f596c8,
    s=3D19) at stl_map.h:221
#3  0x0081d5e7 in FIX::ThreadedSocketAcceptor::socketThread =
(p=3D0xf6a8a10)
    at ThreadedSocketConnection.h:51
#4  0x00cb7dec in start_thread () from /lib/tls/libpthread.so.0
#5  0x006f0a2a in clone () from /lib/tls/libc.so.6

At Level #2, the Acceptor member m_threads shows a suspicious =
"_M_node_count
=3D 0" which can lead to the thread=3D0 passed to thread_detach and =
causes the
segfault

I'm not sure if faulty code on my side can lead to that errors, but i've
found that problem in all my developments using a ThreadAcceptor, =
ranging
from a single FIX logger to a monstrous routing system.

I'm compiling QFix with mysql support (MySQL ver 4.14) on RedHat =
Enterprise
3 servers.
Some system libs:
glibc-devel-2.3.2.-95.3x (pthreads)
libstdc++-devel-3.2.3-52 (stl)

Thanks in advance and cheers (again) for your great work

Guillermo


****************************** AVISO LEGAL =
******************************
La informaci=F3n contenida en este mensaje es para uso exclusivo de su =
destinatario. No debe copiarse, transmitirse a terceros ni guardarse por =
estos =FAltimos, salvo autorizaci=F3n del remitente.
Puede contener informaci=F3n confidencial o legalmente protegida cuyo =
r=E9gimen legal de utilizaci=F3n no se ve afectado por el hecho de que =
haya sido enviada por correo electr=F3nico.
Su env=EDo por error a una persona distinta de su destinatario real no =
implica que se haya modificado tal destinatario ni supone renuncia a su =
eventual car=E1cter confidencial o al r=E9gimen legal que rija su =
utilizaci=F3n.
Cualquier opini=F3n expresada en este mensaje vincular=E1 exclusivamente =
a la persona que lo haya remitido, excepto cuando el mensaje establezca =
lo contrario y el remitente est=E9 autorizado para establecer que dichas =
opiniones vincular=E1n a esta entidad.
En el supuesto de que este correo se recibiera por error, rogamos =
procedan a borrarlo, sin reenviarlo a terceros ni conservarlo en =
cualquier soporte y nos informen inmediatamente llamando al tel=E9fono =
34 91 5892123 o a la direcci=F3n de correo electr=F3nico remitente. =
Gracias.
****************************** DISCLAIMER ******************************
The information contained in this message is for the exclusive use of =
the named person. It can not be copied, transmitted to third parties or =
stored by the latter, except if authorised by the sender.
It may contain confidential or legally privileged information whose =
legal regime is not affected by the fact that this information has been =
sent by e-mail.=20
Its erroneous transmission to a person other than the real named person =
neither implies any modification of this named person nor a renunciation =
of the eventual confidentiality or legal regime affecting the use of =
concerned message.
Any views expressed in this message are binding exclusively upon the =
individual sender, except where the message states otherwise and the =
sender is authorised to bind this entity.=20
If you receive this message in error, please delete it without =
transmitting it to any third party or keeping it in any form and notify =
us immediately either by phone (34 91 5892123) or using the e- mail =
address of the sender. Thank You.