Archived

This forum has been archived. Please start a new discussion on GitHub.

Service crashed in readTypeId ()

During some ice operations crash happened with a stack below. Could you point what caused the problem? Ice version 3.2.1, debian.
#0 0xf7d7847e in IceInternal::BasicStream::readTypeId () from /usr/lib/libIce.so.32
(gdb) bt
#0 0xf7d7847e in IceInternal::BasicStream::readTypeId () from /usr/lib/libIce.so.32
#1 0xf7d78e5f in IceInternal::BasicStream::read () from /usr/lib/libIce.so.32
#2 0xf7d79b64 in IceInternal::BasicStream::readPendingObjects () from /usr/lib/libIce.so.32 
#3 0x08144e5d in servant::Servant::___setServants (this=0x82fc8c0, __inS=@0xf338cd6c, __current=@0xf338cd6c) at ../common_ifaces/servant.cpp:16163 
#4 0x08182bd9 in servant::ServantObj::__dispatch (this=0x82fc8c0, in=@0xf338cd6c, current=@0xf338cd6c) at ../common_ifaces/servant.cpp:16460 
#5 0xf7dcb83b in IceInternal::Incoming::invoke () from /usr/lib/libIce.so.32 
#6 0xf7d9df42 in Ice::ConnectionI::invokeAll () from /usr/lib/libIce.so.32 
#7 0xf7da4d92 in Ice::ConnectionI::message () from /usr/lib/libIce.so.32 
#8 0xf7e9a98f in IceInternal::ThreadPool::run () from /usr/lib/libIce.so.32 
#9 0xf7e9c78f in IceInternal::ThreadPool::EventHandlerThread::run () from /usr/lib/libIce.so.32 
#10 0xf79d5a56 in IceUtil::Thread::~Thread () from /usr/lib/libIceUtil.so.32 
#11 0xf799e0bd in start_thread () from /lib/tls/libpthread.so.0 
#12 0xf7aae01e in clone () from /lib/tls/libc.so.6

Comments

  • benoit
    benoit Rennes, France
    Hi,

    I'm afraid it's difficult to say without more information. From the stack trace, it looks like a crash during the un-marshalling of some Ice objects, this of course shouldn't happen (either there's a bug in Ice or your process memory gets corrupted somehow).

    Is this something you can reproduce easily? Could you by any chance reproduce it with a debug build of Ice?

    Cheers,
    Benoit.
  • It happens rarely. As far as I understood it could be determined only by exploring core files + ICE source code, fortunately it's possible thanks to ZeroC development model.