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

Fri Jun 29 11:39:58 CDT 2007

Hi Jules,

> Is there some way to turn on debug logging in the reactor so I can
see
> what it's up to?  Might that shed some light on the problem?

You can rebuild ACE with tracing on, but that'll produce a ton of
output. It'd be much quicker to run with valgrind and let it do the
hard work for you.

> Jules.
> 
> 
> -----Original Message-----
> From: Steve Huston [mailto:shuston at riverace.com] 
> Sent: Friday, June 29, 2007 12:15 PM
> To: Jules d'Entremont; ace-users at cse.wustl.edu
> Subject: RE: [ace-users] Segmentation fault
> inACE_Select_Reactor_T::handle_error (with ACE 5.5.9)
> 
> > What qualifies as a bad handle?
> 
> Anything that select() doesn't like ;-)
> 
> > Is a closed ACE_SOCK_Stream a bad handle?
>  
> Yes.
> 
> -Steve
> 
> 
> From: Steve Huston [mailto:shuston at riverace.com] 
> Sent: Friday, June 29, 2007 11:57 AM
> To: Jules d'Entremont; ace-users at cse.wustl.edu
> Subject: RE: [ace-users] Segmentation fault
> inACE_Select_Reactor_T::handle_error (with ACE 5.5.9)
>  
> Hi Jules,
>  
> Thanks for the PROBLEM-REPORT-FORM.
>  
> >From the looks of the args in the stack trace, your reactor is (at
> least partly) smashed. And, it's trying to recover from a bad handle
> in the registered handle set. If that doesn't shed any light on
> things, try running this under valgrind to see if it can focus you
on
> the problem area.
>  
> -Steve
> --
> Steve Huston, Riverace Corporation
> Would you like ACE to run great on your platform?
> See http://www.riverace.com/sponsor.htm
> -----Original Message-----
> From: ace-users-bounces at cse.wustl.edu
> [mailto:ace-users-bounces at cse.wustl.edu] On Behalf Of Jules
> d'Entremont
> Sent: Friday, June 29, 2007 11:38 AM
> To: ace-users at cse.wustl.edu
> Subject: [ace-users] Segmentation fault
> inACE_Select_Reactor_T::handle_error (with ACE 5.5.9)
>     ACE VERSION: 5.5.9
>  
>     HOST MACHINE and OPERATING SYSTEM:
>         Linux dev228 2.6.11.11sol-pe #1 SMP Thu Aug 25 13:56:24 EDT
> 2005 i686 i686 i386 GNU/Linux
>  
>     TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
>     COMPILER NAME AND VERSION (AND PATCHLEVEL):  
>       g++ (GCC) 3.3.2
>  
>     THE $ACE_ROOT/ace/config.h FILE [if you use a link to a
> platform-specific file, simply state which one]:  
>        #include "config-linux.h"
>  
>     THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE [if
you
>     use a link to a platform-specific file, simply state which one
>     (unless this isn't used in this case, e.g., with Microsoft
Visual
>     C++)]:   platform_linux.GNU
>  
>     CONTENTS OF
> $ACE_ROOT/bin/MakeProjectCreator/config/default.features
>     (used by MPC when you generate your own makefiles):
>  
>     AREA/CLASS/EXAMPLE AFFECTED:
>  
>     DOES THE PROBLEM AFFECT:
>         COMPILATION?
>         LINKING?
>             On Unix systems, did you run make realclean first?
>         EXECUTION?  yes
>         OTHER (please specify)?
>  
>     SYNOPSIS:
>  
>     DESCRIPTION:
> I've recently been getting segmentation faults in my ACE
application,
> which I'm at a loss to explain.  Here's the stack trace:
>  
> (gdb) where
> #0  0xb7f9a767 in ACE_Select_Reactor_Handler_Repository::unbind
> (this=0x8108074, handle=135368392, pos=0x8118ec8, mask=511) at
> Select_Reactor_Base.cpp:397
> #1  0xb7f3e21a in
ACE_Select_Reactor_T<ACE_Reactor_Token_T<ACE_Token>
> >::remove_handler_i (this=0x8108070, handle=5, mask=135368408)
>     at
>
/home/jdentremont/src/ACE-5.5.9/ACE_wrappers/ace/Select_Reactor_T.cpp:
> 1012
> #2  0xb7f3edaa in
ACE_Select_Reactor_T<ACE_Reactor_Token_T<ACE_Token>
> >::check_handles (this=0x8108070) at
>
/home/jdentremont/src/ACE-5.5.9/ACE_wrappers/ace/Select_Reactor_T.cpp:
> 1526
> #3  0xb7f3ee1b in
ACE_Select_Reactor_T<ACE_Reactor_Token_T<ACE_Token>
> >::handle_error (this=0x8108070) at
>
/home/jdentremont/src/ACE-5.5.9/ACE_wrappers/ace/Select_Reactor_T.cpp:
> 788
> #4  0xb7f3bfde in
ACE_Select_Reactor_T<ACE_Reactor_Token_T<ACE_Token>
> >::wait_for_multiple_events (this=0x8108070,
dispatch_set=@0x810808c,
> max_wait_time=0x0)
>     at
>
/home/jdentremont/src/ACE-5.5.9/ACE_wrappers/ace/Select_Reactor_T.cpp:
> 1104
> #5  0xb7f40250 in
ACE_Select_Reactor_T<ACE_Reactor_Token_T<ACE_Token>
> >::handle_events_i (this=0x8108070, max_wait_time=0x1ff)
>     at
>
/home/jdentremont/src/ACE-5.5.9/ACE_wrappers/ace/Select_Reactor_T.cpp:
> 1443
> #6  0xb7f3c227 in
ACE_Select_Reactor_T<ACE_Reactor_Token_T<ACE_Token>
> >::handle_events (this=0x8108070, max_wait_time=0x0)
>     at
>
/home/jdentremont/src/ACE-5.5.9/ACE_wrappers/ace/Select_Reactor_T.cpp:
> 1424
> #7  0xb7f97a06 in ACE_Reactor::run_reactor_event_loop
(this=0x8107180,
> eh=0) at Reactor.cpp:233
> #8  0x08079d69 in (anonymous namespace)::ReactorThread::svc
> (this=0x8110d00) at
>
/home/jdentremont/svn/branches/d14_branch/cppcsmp/CSMPFactory.cpp:131
> #9  0xb7face24 in ACE_Task_Base::svc_run (args=0x8110d00) at
> Task.cpp:271
> #10 0xb7fad29c in ACE_Thread_Adapter::invoke_i (this=0x8118ed8) at
> Thread_Adapter.cpp:146
> #11 0xb7fad1f6 in ACE_Thread_Adapter::invoke (this=0x810fab0) at
> Thread_Adapter.cpp:95
> #12 0xb7f42651 in ace_thread_adapter (args=0x1ff) at
> Base_Thread_Adapter.cpp:116
> #13 0x006c1b80 in start_thread () from /lib/libpthread.so.0
> #14 0x00619dee in clone () from /lib/libc.so.6
>  
> I don't know where to start to try to debug this.  Any insight that
> anyone could offer would be greatly appreciated.  I was hoping that
> this was caused by bug 2653, but I'm still seeing it with ACE 5.5.9.
>  
> Thanks.
>  
> Jules d'Entremont
>  
>  
> 
> 
> 