[omniNotify] Re: omninotify-list Digest, Vol 30, Issue 1

Ronan Heffernan ronansan at gmail.com
Thu Dec 14 12:37:09 GMT 2006


Mark,
   Is this a new project, or has your client code been running against
omniNotify for a while?  Has anything changed (client, OS, hardware,
omniNotify version, etc)?  It sounds like you cannot re-create this problem
at will?  If you have any idea how to re-create this, or an approximate
frequency (once per 10,000 events, once every 3 days), please let us know.

   Also, can you provide: omniNotify version, omniORB version, compiler
version (gcc v3?), etc.  Is the problem always in
SupplierAdmin_i::obj_gc()?  Is your client/supplier code proprietary, or can
you provide that as well?  I don't have any Solaris boxes at my disposal,
but I will research it as much as possible.  Thanks.

--ronan



Date: Wed, 13 Dec 2006 13:58:52 -0700
> From: Mark Zimmerman <markzimm at frii.com>
> Subject: [omniNotify] Occasional notifd crash
> To: omninotify-list at omniorb-support.com
> Message-ID: <20061213205852.GA4641 at io.frii.com>
> Content-Type: text/plain; charset=us-ascii
>
> Greetings:
>
> I am starting to see occasional core dumps of notifd under Solaris 9
> (sparc). I don't have a lot of information yet but I thought I would
> throw this out here in case anyone is still reading this list and has
> insight or experience with this one.
>
> The following line showed up in the debug printout:
>
> DBG[lib/RDIOplocks.cc:458]: *** Internal error: RDIOplocks::free_entry
> called with an entry that appears to already be on the free list
>
> Then, some time later a core dump occurred. The core file shows this:
>
> t at 15 (l at 15) terminated by signal SEGV (no mapping at the fault address)
> 0x7fffffff7f9c72dc: acquire+0x0004:     ldx      [%i0 + 80], %i2
> Current function is omni_thread_wrapper (optimized)
>   451           me->run(me->thread_arg);
> (dbx) where
> current thread: t at 15
>   [1] RDIOplockEntry::acquire(0x8a8d20, 0x1008c9230, 0x0,
> 0x7fffffff7ed39f40, 0x
> 1c48, 0x8a8d20), at 0x7fffffff7f9c72dc
>   [2] SupplierAdmin_i::obj_gc(0x7fffffff7fba1fc8, 0x1008c9230, 0x0, 0x0,
> 0x258,
> 0x7fffffff7a3fbae4), at 0x7fffffff7f8d4538
>   [3] EventChannel_i::gcollect(0x100160830, 0x5, 0x7fffffff7a3fbca8, 0x4,
> 0x10,
> 0x5), at 0x7fffffff7f929b54
> =>[4] omni_thread_wrapper(ptr = ???) (optimized), at 0x7fffffff7e203708
> (line ~4
> 51) in "posix.cc"
>
>
> This was running at a remote site with practically all debug and
> reporting turned off, unfortunately.
>
> -- Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omninotify-list/attachments/20061214/5471e567/attachment-0001.htm


More information about the omninotify-list mailing list