[ace-users] Segmentation faultinACE_Select_Reactor_T::handle_error (with ACE 5.5.9)

[Steve Huston]

You could check errno on return and read the code to find out why
that's happening.

--
Steve Huston, Riverace Corporation
Would you like ACE to run great on your platform?
See http://www.riverace.com/sponsor.htm


> -----Original Message-----
> From: Jules d'Entremont [mailto:Jules.dEntremont at SolaceSystems.com] 
> Sent: Friday, June 29, 2007 2:27 PM
> To: Steve Huston; ace-users at cse.wustl.edu
> Subject: RE: [ace-users] Segmentation 
> faultinACE_Select_Reactor_T::handle_error (with ACE 5.5.9)
> 
> 
> I'm getting -1 returned from remove_handler().  I assume that's bad.
> How can I find out why it's failing?
> 
> Jules.
> 
> 
> -----Original Message-----
> From: Steve Huston [mailto:shuston at riverace.com] 
> Sent: Friday, June 29, 2007 2:05 PM
> To: Jules d'Entremont; ace-users at cse.wustl.edu
> Subject: RE: [ace-users] Segmentation
> faultinACE_Select_Reactor_T::handle_error (with ACE 5.5.9)
> 
> Hi Jules,
> 
> > Actually, I spoke too soon.  Here's something I got from valgrind:
> > 
> > ==29898== Invalid read of size 4
> 
> Yup, that'd do it ;-)
> 
> > This seems to indicate that a MessageReader (which is derived from
> > ACE_Event_Handler) gets deleted while still registered with the
> reactor.
> 
> Yes, exactly.
> 
> > But it should get cleaned up in handle_close():
> 
> The evidence suggests that something remains not cleaned up. I'd
have
> a closer look at the remove_handler() call with an eye toward how a
> handle could get left registered.
> 
> -Steve
>  
> 
>