RE: epics php

["Jeff Hill" <johill@lanl.gov>]

Hello Christophe,


What EPICS base version supplies the CA client library that is running when
this occurs?

> It seems that there is a problem with the thread primitives but we did
> not manage to know what was going on.

The stack trace reported below looks like the normal typical place where the
thread being examined parks when it is idle. Do you know for certain that
this is the thread that experiences the segmentation fault (typically GDB
*will* be pointing at the thread that faulted if it is attached when the
fault occurs)? With command line gdb one can type "info threads" and "thread
nnn" to switch threads. However, the most efferent way to switch threads in
the GDB debugger on Linux will be to run a GUI debugger such as ddd. I will
be happy to look at the back traces from all of the threads involved if you
send them in an email.

I am postponing creation of a new mantis entry until we have a bit more
information on the problem. You can also create your own entry in the Mantis
bug tracker as you see fit.

Jeff

> -----Original Message-----
> From: Christophe Moins [mailto:christophe.moins@ego-gw.it]
> Sent: Monday, June 19, 2006 4:02 AM
> To: tech-talk@aps.anl.gov
> Subject: epics php
> 
> Hello,
> 
> we run a php script using the epics php module with the command line
> tool under gdb on a Redhat 9.0-3  machine with kernel 2.4.20-9.
> A segmentation fault shows up periodically and here is what we get with
> the bt command under gdb :
> 
> 
> #0  0xffffe002 in ?? ()
> #1  0x402d984e in epicsEventWait (pevent=0x0)
>    at ../../../src/libCom/osi/os/posix/osdEvent.c:75
> #2  0x402d3d3e in epicsEvent::wait() (this=0xfffffffc)
>    at ../../../src/libCom/osi/epicsEvent.cpp:63
> #3  0x40322dfd in tcpSendThread::run() (this=0x81e6d30)
> at ../tcpiiu.cpp:85
> #4  0x402d2118 in epicsThreadCallEntryPoint (pPvt=0x81e6d34)
>    at ../../../src/libCom/osi/epicsThread.cpp:59
> #5  0x402d8e2f in start_routine (arg=0x81ecd28)
>    at ../../../src/libCom/osi/os/posix/osdThread.c:301
> #6  0x400222b6 in start_thread () from /lib/tls/libpthread.so.0
> 
> 
> It seems that there is a problem with the thread primitives but we did
> not manage to know what was going on.
> Do you have any idea ?
> 
> Thanks
> Christophe