Re: [Fresco-devel] some fixes for client-exit-problems

[email protected] Sun, 19 Oct 2003 16:35:10 +0200
Newsgroups gmane.comp.video.fresco.devel
Message-ID <20031019143510.GA28394@balthasar>
On Sun, Oct 19, 2003 at 08:51:57AM -0400, Nick Lewycky wrote:
> [email protected] wrote:
> >problem:
> >if you interact with clients while this clients exit the server tends to 
> >crash. for example click
> >at [X] and try to move the window as fast as you can... as far as i see 
> >the problem is if
> >the EventManager wants to damage a always dead graphic... i simply fix 
> >this by inserting the
> >(*i)->damage(r); call in a try {} catch (const CORBA::OBJECT_NOT_EXIST &) 
> >{} block. is this the right place to catch this exception? i don't know...
> 
> Wait, I'm confused. That code in EventManager::damage isn't calling into 
>  a Graphic, it's calling into PositionalFocus or NonPositionalFocus. 
> Neither PositionalFocus nor NonPositionalFocus ::damage deal with 
> Graphics themselves. Where's the exception being thrown from? If you 
> turn on trace, does it show PositionalFocus::damage being entered?

yes! the focus-objects are not dead... your right... the exception is trown
in TraversalImpl::update() called by PositionalFocus::damage().

#8  0x400a6c00 in omni::omniExHelper::OBJECT_NOT_EXIST(char const*, int, unsigned long, CORBA::CompletionStatus) () from /usr/local/lib/libomniORB4.so.0
#9  0x400c4ed5 in omniObjRef::_invoke(omniCallDescriptor&, bool) () from /usr/local/lib/libomniORB4.so.0
#10 0x40666901 in Fresco::_objref_Graphic::allocate(unsigned long, Fresco::Allocation::Info const&) (this=0x858b7b8, t=0, i=@0xbedff6ec) at GraphicSK.cc:1300
#11 0x408e74bd in TraversalImpl::update() (this=0x8105ea0) at TraversalImpl.cc:154
#12 0x408e7d0b in virtual thunk to TraversalImpl::update() () from /usr/local/lib/libBerlin.so
#13 0x4092517b in PositionalFocus::damage(Fresco::_objref_Region*) (this=0x80f5d60, region=0x83d3138) at PositionalFocus.cc:247
#14 0x40921bb4 in EventManager::damage(Fresco::_objref_Region*) (this=0x80f5bc0, r=0x83d3138) at EventManager.cc:105

> (I'll try to reproduce it myself if I can, but it sounds like a tricky 
> sort of timing issue is necessary to do so.)
> 
> Nick Lewycky
> 
> 
> _______________________________________________
> Fresco-devel mailing list
> [email protected]
> http://lists.fresco.org/cgi-bin/listinfo/fresco-devel
>