Re: [mico-devel] _non_existent() fails sometimes even when the service is active

2016-02-22 Thread Rob Ratcliff
if you are able to duplicate on HEAD or not. > > Thanks, > Karel > > On 11/27/15 11:19 PM, Rob Ratcliff wrote: >> Hi Karel, >> >> The version of MICO I am working with is from December 2, 2011. I tried >> the most recent version from darcs, but I cannot load IDL i

Re: [mico-devel] _non_existent() fails sometimes even when the service is active

2015-11-27 Thread Rob Ratcliff
ion I mean either release number > or what is your last patch in darcs repo if you use repo. > > Thanks, > Karel > > On 11/27/15 07:56 PM, Rob Ratcliff wrote: >> Hi, >> >> We've noticed recently that calls to _non_existent() are coming back >> true even

[mico-devel] _non_existent() fails sometimes even when the service is active

2015-11-27 Thread Rob Ratcliff
Hi, We've noticed recently that calls to _non_existent() are coming back true even when the remove object is active and the communication thread on the remove is blocked for a period due to it being busy with tasking. (We are currently running MICO single threaded currently due to using Combat.) I

Re: [mico-devel] idl compiled multi-threaded core dumps when loading CORBA.idl

2011-10-26 Thread Rob Ratcliff
Looks like some lookup table in the ird gets corrupted, since it appears that the "ird" thinks that the given "OperationDef" is_a Container since this code returns "True" where obj is a "OperationDef" and repoid is "IDL:omg.org/CORBA/Container:1.0: object.cc: (called from ir.cc below) CORBA::Bo

Re: [mico-devel] idl compiled multi-threaded core dumps when loading CORBA.idl

2011-10-25 Thread Rob Ratcliff
{ _o = new CORBA::Container_stub; _o->CORBA::Object::operator=( *_obj ); return _o; } } return _nil(); } On 10/25/2011 10:25 PM, Rob Ratcliff wrote: > Here's more info on the problem: > > When I defined the method in the IDL as: > >JobIds getFailedJo

Re: [mico-devel] idl compiled multi-threaded core dumps when loading CORBA.idl

2011-10-25 Thread Rob Ratcliff
ummy2 = CORBA::Container::_narrow (contents[i]); if (!CORBA::is_nil (dummy2)) { if (!copy (dummy2, _feed_included_defs)) { return false; } } } return true; } On 10/23/2011 11:35 PM, Rob Ratcliff wrote: > Karel, > > I haven't found the root cause of the

Re: [mico-devel] idl compiled multi-threaded core dumps when loading CORBA.idl

2011-10-23 Thread Rob Ratcliff
n >> communicating with the multi-threaded ird, but not with the single-threaded >> ird. So it appears that the crash is related to enabling >> threads in the ird. >> >> On 10/18/2011 10:04 AM, Rob Ratcliff wrote: >>> Hi, >>> >>> I c

Re: [mico-devel] idl compiled multi-threaded core dumps when loading CORBA.idl

2011-10-19 Thread Rob Ratcliff
0x80893d1]Abort (core dumped) On 10/19/2011 08:31 AM, Rob Ratcliff wrote: > Here's another update: I recompiled mico with threads disabled and noticed > that the single-threaded idl program crashed when > communicating with the multi-threaded ird, but not with the single-threaded >

Re: [mico-devel] idl compiled multi-threaded core dumps when loading CORBA.idl

2011-10-19 Thread Rob Ratcliff
11 10:04 AM, Rob Ratcliff wrote: > Hi, > > I compiled MICO with multi-thread enabled (and CSIV2). When I attempt to load > the CORBA.idl into the interface repository using > idl --feed-ir CORBA.idl > > I get the following stack trace from the core dump: > >

[mico-devel] Multi-threaded Interface Repository core dumps when loading CORBA.idl

2011-10-18 Thread Rob Ratcliff
Hi, I compiled MICO with multi-thread enabled (and CSIV2). When I attempt to load the CORBA.idl into the interface repository using idl --feed-ir CORBA.idl I get the following stack trace from the core dump: (gdb) where #0 0x0013a416 in __kernel_vsyscall () #1 0x003052f1 in raise () from /lib

[mico-devel] idl compiled multi-threaded core dumps when loading CORBA.idl

2011-10-18 Thread Rob Ratcliff
Hi, I compiled MICO with multi-thread enabled (and CSIV2). When I attempt to load the CORBA.idl into the interface repository using idl --feed-ir CORBA.idl I get the following stack trace from the core dump: (gdb) where #0 0x0013a416 in __kernel_vsyscall () #1 0x003052f1 in raise () from /lib