[omniORB] RE: serious stability problems with omniORB4 snapshots on Solaris 8

Rosimildo daSilva rdasilva@connecttel.com
Thu, 31 Jan 2002 10:47:10 -0600


From: Duncan Grisby <dgrisby@uk.research.att.com>
To: Bastiaan Bakker <Bastiaan.Bakker@lifeline.nl>
Cc: omniorb-list@uk.research.att.com <omniorb-list@uk.research.att.com>
Date: Thursday, January 31, 2002 10:44 AM
Subject: Re: [omniORB] RE: serious stability problems with omniORB4
snapshots on Solaris 8


>On Thursday 31 January, "Bastiaan Bakker" wrote:
>
>Most likely, though, it's a bug in the new omniORB transport code. Try
>running with a high trace level to see if that prints anything
>interesting before the crash (if it's a race condition, the tracing
>might prevent it, of course...). To get a handle on when the
>connection is deleted, try adding tracing to the destructor. If you
>print out the this pointer, that'll help you find the relevant
>destruction when the crash happens. Code something like:
>
>  {
>    omniORB::logger l;
>    l << "connection deleted: " << (void*)this << "\n";
>  }
>


Duncan,  you *read my mind*. :-)

I usually log the *this* point at the Ctor and Dtor and check whether they
balance,
and when it happens.

Rosimildo.