RE: [Quickfix-developers] Re: ThreadedSocketAcceptor Segmentation Faults

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

Also note that the thread that FIX::thread_detach() receives is 0. I =
think
that's the segfault cause. Also i think the threads are joined =
previously,
when Acceptor::stop is called. The threads are detached when the
Socket->Read() loop ends and so the thread does.

If this strange behaviour is happening only to Alberto and me we really
should start looking at dependencies and installed libraries to =
determine
where the incompatibility may lay on.

Cheers for your work,

Guillermo
  -----Mensaje original-----
  De: qui...@li...
[mailto:qui...@li...]En nombre de =
Caleb
Epstein
  Enviado el: martes, 08 de noviembre de 2005 14:13
  Para: Alberto Bellido Rodr=EDguez
  CC: qui...@li...
  Asunto: Re: [Quickfix-developers] Re: ThreadedSocketAcceptor =
Segmentation
Faults




  On 11/8/05, Alberto Bellido Rodr=EDguez <bellido@3.14financial.com> =
wrote:


    #0  0x4048318c in pthread_detach () from /lib/tls/libpthread.so.0
    #1  0x400d5edc in FIX::thread_detach (thread=3D0) at Utility.cpp:344
    #2  0x4009323f in FIX::ThreadedSocketAcceptor::removeThread
    (this=3D0xbffff500, s=3D57) at stl_map.h:332
    #3  0x40093335 in FIX::ThreadedSocketAcceptor::socketThread =
(p=3D0x3) at
    ThreadedSocketConnection.h:51
    #4  0x40482b3c in start_thread () from /lib/tls/libpthread.so.0
    #5  0x4032092a in clone () from /lib/tls/libc.so.6

  I really think this call should be changed to a thread_join, at least =
on
UNIX systems.  Detaching a running thread seems like playing Russion
Roulette to me.


  --
  Caleb Epstein
  caleb dot epstein at gmail dot com


****************************** 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.