Hello,

I have got the latest svn of sipXtapi to compile and build libraries on
my Centos 5.1 system. However when I compile, link and run my
application against the libraries I get an assertion error in one of the
tapi threads.

The thread where the error is generated is stack is

/lib/libc.so.6
/lib/libpthread.so.0
os/linux/OsTaskLinux.cpp:713
os/OsServerTask.cpp:157
os/OsServerTask.cpp:135
os/shared/OsMsgQShared.cpp:121
os/shared/OsMsgQShared.cpp:367

The bit of code that generates the OS_WAIT_TIMEOUT (actually OS_BUSY)
value is OsStatus OsMsgQShared::doReceive(OsMsg*& rpMsg, const OsTime&
rTimeout)

...

   ret = mFull.acquire(rTimeout);  // wait for a message to be available
   if (ret != OS_SUCCESS)
   {
      if (ret == OS_BUSY || ret == OS_WAIT_TIMEOUT)
         ret = OS_WAIT_TIMEOUT;   // receive timed out
      else
      {
         assert(FALSE);
         ret = OS_UNSPECIFIED;
      }
   }

And that causes an assertion failure in int OsServerTask::run(void* pArg)
...

   do
   {
      res = receiveMessage((OsMsg*&) pMsg);          // wait for a message
      assert(res == OS_SUCCESS);


Notes:

1. The sample applications ReceiveCall works O.K. when using make in the
svn tree
2. My application is compiled and debugged under kdevelop with the
includes and libraries pointed to the svn version.
3. I have the original - May 07, not svn - libraries in my library path.
3. The debugger is using the svn version of the libraries which seems to
indicate I am not mixing my libraries
4. Several other sipXtapi threads started O.K.
5. The error occurs before I call any sipXtapi functions so I assume it
is to do with initialization of global data within the tapi?

Any advice appreciated.

Thanks


_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/

Reply via email to