Re: [mico-devel] Why is CosEventComm::PushConsumer_skel no longer generated in 2.3.13?

[Karel Gardas]

Guys,

you should really concentrate your energy on bringing your code up to
the MICO 2.3.13 compatibility. Please keep in mind that BOA is more than
10 years deprecated already! IIRC POA was specified in 1998...

It's not that hard at the end, and for your information we usually do
this during one or two days on-site consulting/training at the customer
office after which customer is able to port all their sources successfully.

Cheers,
Karel

Kretschel Klaus wrote:
 Hi Andreas,
 
 On Friday 16 January 2009 13:49, Andreas Benzler wrote:
 I am highly interested in your approach bringing mico 2.3.11 to a gcc4.3
 platform. Can you please describe a bit more detail what you did
 exactly. I am not an automake expert :-(.
 
 I did nothing but replace configure and configure.in from the mico 2.3.13 
 distribution. There is on thing more that I had fixed earlier: add #include 
 cstring in throw.h. Then follow the usual install procedure.
 
 However, I was possibly a little too fast, although I am not sure if the 
 error 
 I just got has really to do with MICO, but it seem to me that something is 
 not cleaned up correctly. I got a segmentation fault at the very end of a 
 test program that did not even use MICO services:
 
 Program received signal SIGSEGV, Segmentation fault.
 0x0021 in ?? ()
 (gdb) up
 #1  0x7fd364e36628 in __cxa_finalize () from /lib64/libc.so.6
 (gdb) up
 #2  0x7fd36866ad66 in __do_global_dtors_aux () from Current language:  
 auto; currently asm
 (gdb) up
 #3  0x0046fc90 in std::basic_ioschar, std::char_traitschar 
 ::basic_ios ()
 (gdb) up
 #4  0x7fff720e1540 in ?? ()
 (gdb)  up
 #5  0x7fd368873de1 in _fini () 
 from 
 /home/donau101/adsm/scia/ol_level_1_to_2/tools/mico/for-x86_64/mico.2.3.11/lib/libmico2.3.11.so
 (gdb) up
 #6  0x001a in ?? ()
 (gdb) up
 #7  0x7fd369ed4d94 in ?? () from /lib64/ld-linux-x86-64.so.2
 (gdb) up
 Initial frame selected; you cannot go up.
 (gdb) 
 
 Regards,
 Klaus
 ___
 Mico-devel mailing list
 Mico-devel@mico.org
 http://www.mico.org/mailman/listinfo/mico-devel
 


-- 
Karel Gardas  kgar...@objectsecurity.com
ObjectSecurity Ltd.   http://www.objectsecurity.com
___
Mico-devel mailing list
Mico-devel@mico.org
http://www.mico.org/mailman/listinfo/mico-devel

Re: [mico-devel] Why is CosEventComm::PushConsumer_skel no longer generated in 2.3.13?

[Andreas Benzler]

Hi Klaus

I am highly interested in your approach bringing mico 2.3.11 to a gcc4.3
platform. Can you please describe a bit more detail what you did
exactly. I am not an automake expert :-(.
If you could make a patch available for 2.3.11 it would be even better...

Regards

Andreas Benzler


Kretschel Klaus schrieb:
 Hi Karel,
 
 On Wednesday 14 January 2009 15:41, Karel Gardas wrote:
 exactly! MICO 2.3.13 does not support BOA anymore. For your information,
 your CosEventComm::PushConsumer_skel is BOA's skeleton code. My best
 advice to you is to update code to use POA's skeletons. Hmm, why do you
 need to use skeleton code exactly? It's used just by service
 implementors, isn't it? Or are you writing your own event service? If
 so, then ok...
 
 it's old code written by someone else, and I guess it is not necessary. Can 
 you recommend some useful documentation for POA event service? The Puder book 
 does not even mention the event service...
 
 But we will not need to upgrade by now. Using the configure scripts from 
 2.3.13 allowed also to compile 2.3.11 with gcc 4.3. The key was 
 the -fno-strict-aliasing option.
 
 Best regards,
 Klaus
 ___
 Mico-devel mailing list
 Mico-devel@mico.org
 http://www.mico.org/mailman/listinfo/mico-devel
 
___
Mico-devel mailing list
Mico-devel@mico.org
http://www.mico.org/mailman/listinfo/mico-devel