Re: SIGSEGV in eventd

Hi Thomas,

could you be so kind and duplicate your issue with this snapshot: 
http://www.mico.org/snapshots/mico-2011-03-11.tar.bz2

If you are able to duplicate it, I would appreciate if you can provide 
as simple as possible test case for it (compilable/runnable on Unix 
preferably)

Thanks,
Karel

On 03/10/11 10:44 PM, Thomas Schmidt wrote:
> Hi,
>
> when running some experimental stuff I got SIGSEGV on first pull() from an event channel.
>
> I created an event channel connected to a pull supplier (a `long´ random number generator) on one end and
to a pull consumer on the other one. When pulling from the channels reading end I get exactly one random
number - then the event channel daemon (eventd) crashes with SIGSEGV. Here is a stack backtrace:
>
> #0	0x10037ee7a in MICO::IIOPServerInvokeRec::~IIOPServerInvokeRec
> #1	0x1003894b1 in MICO::IIOPServer::del_invoke_orbid
> #2	0x10038a5be in MICO::IIOPServer::handle_invoke_reply
> #3	0x1003b5390 in CORBA::StaticServerRequest::~StaticServerRequest
> #4	0x1000012ab in CORBA::release at object.h:71
> #5	0x10000952d in ObjVar<CORBA::StaticServerRequest>::release at template_impl.h:49
> #6	0x10000954e in ObjVar<CORBA::StaticServerRequest>::free at template.h:139
> #7	0x10000957b in ObjVar<CORBA::StaticServerRequest>::~ObjVar at template.h:74
> #8	0x100004fa0 in ProxyPullSupplier_impl::notify at CosEvent_impl.cc:323
> #9	0x10008ca47 in CosEventChannelAdmin::ProxyPullSupplier_stub_clp::notify
> #10	0x1000027da in EventChannel_impl::notify at CosEvent_impl.cc:600
> #11	0x1000046d3 in ProxyPullConsumer_impl::callback at CosEvent_impl.cc:380
> #12	0x1003846ac in MICO::IIOPProxy::exec_invoke_reply
> #13	0x100392703 in MICO::IIOPProxy::handle_invoke_reply
> #14	0x100393096 in MICO::IIOPProxy::handle_input
> #15	0x1003938e9 in MICO::IIOPProxy::input_callback
> #16	0x10038c648 in MICO::GIOPConn::input_ready
> #17	0x10038ce89 in MICO::GIOPConn::do_read
> #18	0x100343b11 in MICO::SelectDispatcher::handle_fevents
> #19	0x100345937 in MICO::SelectDispatcher::run
> #20	0x1003947bf in MICO::GIOPConnReader::_run
> #21	0x1004cf387 in MICOMT::Thread::_thr_startup
> #22	0x1004cf4ac in MICOMT::Thread::ThreadWrapper
> #23	0x7fff83f91536 in _pthread_start
> #24	0x7fff83f913e9 in thread_start
>
> The crash is reproduceable each time when using a situation as described above.
>
>
> My configuration:
>
>> uname -a
> Darwin Aprilia.local 10.6.0 Darwin Kernel Version 10.6.0: Wed Nov 10 18:13:17 PST 2010;
root:xnu-1504.9.26~3/RELEASE_I386 i386
>
>> cat /usr/local/include/mico/version.h
> #define MICO_VERSION "2.3.13"
> #define MICO_BIN_VERSION 0x02030d
> I'm using thread support (HAVE_THREAD is defined as 1).
>
>> gcc --version
> i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5664)
>
>
> Is there any help? Thanks
>
> Thomas
>
> --
> Thomas Schmidt
> Am Alten Werk 42-44
> D-21406 Melbeck
> Cellular: +49-151-15601126
> Skype: ThCSchmidt
> Email: TC.Schmidt <at> gmx.net
> PGP: Key-ID: 0x810B6206
>
>
>
>
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
>
>
>
> _______________________________________________
> Mico-devel mailing list
> Mico-devel <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mico-devel

--

-- 
Karel Gardas                  kgardas <at> objectsecurity.com
ObjectSecurity Ltd.           http://www.objectsecurity.com

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d