[Ace-users] [tao-users] Thread crash in TAO MProfile code.

[Johnny Willemsen]

Hi,

Thanks for using the PRF form. Please first upgrade to x.6.2 and build this
the traditional way with inlining disabled, the autoconf support is
experimental and we don't advice to use it. Hopefully that gives a callstack
that is more helpful to analyze this issue.

Regards,


Johnny Willemsen
Remedy IT
Postbus 101
2650 AC  Berkel en Rodenrijs
The Netherlands
www.theaceorb.nl / www.remedy.nl  

*** Integrated compile and test statistics see
http://scoreboard.theaceorb.nl ***
*** Commercial service and support for ACE/TAO/CIAO             ***
*** See http://www.theaceorb.nl/en/support.html                 ***


"Venkat" <swara101 at yahoo.com> wrote in message
news:<b716ca6a-93e8-4d90-8c3b-e206cdb5dfe1 at s8g2000prg.googlegroups.com>...
> Hello TAO team,
> 
>     TAO VERSION: 1.6.1
>     ACE VERSION: 5.6.1
>     (actually, svn head taken a couple of weeks back)
> 
>     HOST MACHINE and OPERATING SYSTEM:
>       NetBSD, i386
> 
>     TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
>     COMPILER NAME AND VERSION (AND PATCHLEVEL):
>              NetBSD, i386
> 
>     THE $ACE_ROOT/ace/config.h FILE [if you use a link to a platform-
>     specific file, simply state which one]:
>              generation via autoconf
> 
>     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++)]:
>           n/a
> 
>     CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/
> default.features
>     (used by MPC when you generate your own makefiles):
>              ssl
> 
>     AREA/CLASS/EXAMPLE AFFECTED:
> 
>     DOES THE PROBLEM AFFECT:
>         COMPILATION? no
>         LINKING? no
>         EXECUTION? Yes
> 
>     SYNOPSIS:
> 
>         Thread crash in TAO codebase.
> 
>     DESCRIPTION:
> 
> Client is getting service from Server; both are on different nodes.
> Server crashes and restarts. During the period Server is not
> available, Client keeps calling Server, and consumes any exceptions
> due to server is not available. This is happening in the context
> SSLIOP protocol underneath. I'm seeing the following thread crash on
> client side. It's very temporal. I'm not seeing any way to reproduce.
> Any clue from the following stack trace?
> Any feedback is helpful.
> 
>     Program terminated with signal 11, Segmentation fault.  // null
> pointer due to .....?
> (gdb) where
>    #0  TAO_Default_Endpoint_Selector::select_endpoint (this=Variable
> "this" is not available.) at MProfile.inl:65
> #1  0x00007f7ff97f6b6e in TAO::Profile_Transport_Resolver::resolve
> (this=0x7f7ff3dfe440,max_time_val=0x7f7ff3dfe480)
>     at ../../../TAO/tao/Profile_Transport_Resolver.cpp:88#2
> 0x00007f7ff97cccd7 in TAO::Invocation_Adapter::invoke_remote_i
> (this=0x7f7ff3dfe670, stub=Variable "stub" is not available.)
>     at ../../../TAO/tao/Invocation_Adapter.cpp:247
> #3  0x00007f7ff97cd730 in TAO::Invocation_Adapter::invoke_i
> (this=0x7f7ff3dfe670, stub=0x7d8000,
>     details=@0x7f7ff3dfe570) at ../../../TAO/tao/
> Invocation_Adapter.cpp:92
> #4  0x00007f7ff97cd372 in TAO::Invocation_Adapter::invoke
> (this=0x7f7ff3dfe670, ex_data=0x0, ex_count=0)
>     at ../../../TAO/tao/Invocation_Adapter.cpp:50
> 
>     REPEAT BY:
>            It's a temporal behavior. Hard to reproducem, but has been
> seen a couple of times.
> 
>     SAMPLE FIX/WORKAROUND:
>            None, as it is not clear how to reproduce.
> 
> Thanks
> Venkat