[omniORB] Omninames crash : SEGV in strlen

[Allan Kelly]

We've just been doing some load testing and after 4 hours our omniNames
crashed with a segmentation violation in strlen.  Kind of looks like strlen
was passed a null pointer.

Had a look through the other reported incidents of omniNames crashing and
none seem to match this case.  Anyone seen this before?

We're using:
- omniOrb 2.6.1
- Solaris 2.7
- Sun C++ 4.2

The stack trace from the core looked like this (sorry, release build):

current thread: t@1151
=>[1] strlen(0x0, 0x0, 0xff038f88, 0x7efefeff, 0x81010100, 0xff00), at
0xfefb6dec
  [2] _doprnt(0xff34870d, 0x0, 0x0, 0x0, 0xff3dc904, 0x104), at 0xfefffbc8
  [3] fprintf(0xff037c6c, 0xff34870b, 0xff03b58c, 0xff037670, 0x0, 0x0), at
0xff001614
  [4] omniORB::logStream::operator <<(0xff348700, 0x0, 0x19, 0x1a, 0xc,
0x5f696d70), at 0xff30caf0
  [5] omni::objectRelease(0xff348704, 0xff344dac, 0xff33e3e8, 0x0, 0x0,
0xff34c33c), at 0xff2d478c
  [6] GIOP_S::HandleRequest(0xfac07c10, 0xff0b8770, 0xff33e3e8, 0x0,
0x7d63c, 0xff0000), at 0xff2c6564
  [7] GIOP_S::dispatcher(0x6eda0, 0xff0add70, 0xff33e3e8, 0xff26c8f0, 0x0,
0x8146d), at 0xff2c4848

thanks

allan