[omniORB] Thread error?

[Duncan Grisby]

On Wednesday 11 April, Jo Skjermo wrote:

> (gdb)where
> #0  replace (this=0xdee01998, pos=0, n1=0, s=0x806f049 "pid", n2=3) at ./sinst.cc:411
> #1  0xdf6668e2 in __as__t12basic_string3ZcZt18string_char_traits1ZcZt24__default_alloc_template2b0i0PCc () at ./sinst.cc:181
> #2  0x8060ea1 in SMSReceive::getMessage ()
> #3  0x8063913 in getMessage (this=0x8095b90, username=0x8095930 "jule", password=0x8095900 "nisse", provider_ID=0x8097bc0 "bobsWASP") at smsapi.C:24
> #4  0x805da11 in _impl_api::_dispatch ()

It's dying in something to do with C++ string. I'd guess that you have
corrupted the heap some time earlier, possibly by deleting something
twice.

> Also, yesterday we compiled things on Linux (i586) box instead, and
> everything seemed to work great there (at least we sendt a couple of
> mill. messages before we grew tired:)
> 
> BUT, then we found a very strange problem. When we run the server with
> the -ORBtraceLevel flagg sett, the server froze after outputting the IOR,
> and wouldnt take ANY connections.

I don't know what that could be. Can you successfully run the omniORB
example programs like eg2 with the trace level set?

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --