Alexandre,<br><br>fair enough ... you're right ... it's always omniORB which processes the CORBA calls.<br>Thanks a lot for your hint.<br><br>Friedhelm<br><br><div><span class="gmail_quote">On 6/22/07, <b class="gmail_sendername">
Alexandre DENIS</b> <<a href="mailto:Alexandre.Denis@labri.fr">Alexandre.Denis@labri.fr</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Friday 22 June 2007, Friedhelm Wolf wrote:<br><br>> I attatched a core dump which shows, that there are TAO calls made<br>> within a omni ORB requests. Please correct me if I misinterpret this<br>> dump (I'm no expert at all), but it seems, that the symbols don't get
<br>> mingled. (maybe because the whole TAO stuff is dynamically loaded at<br>> runtime).<br><br>This backtrace shows that CORBA::Object::is_nil from omniORB was applied<br>to a TAO object.<br><br>> But I guess the problem with the _CORBA_bad_param_freebuf() error is
<br>> due to global symbols too and so I better find a way to use the ORBs<br>> in two separate<br>> processes.<br><br>Indeed, it would be much better to have different ORBs in different<br>processes.<br><br>-a.
<br><br><br></blockquote></div><br>