For more infomation about this bug, visit
Summary: valgrind complains about object_to_string
Product: RTT
Version: 1.4.0
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: Corba
AssignedTo: orocos-dev [..] ...
ReportedBy: peter [dot] soetens [..] ...
CC: orocos-dev [..] ...
Estimated Hours: 0.0

When running the cdeployer-gnulinux under valgrind, loading a new component
into the process causes the following warning:

==18442==
==18442== Use of uninitialised value of size 4
==18442== at 0x4C6AAF3: CORBA::ORB::object_to_string(CORBA::Object*) (in
/usr/lib/libTAO.so.1.4.7)
==18442== by 0x46AD72A:
RTT::Corba::ControlTaskServer::ControlTaskServer(RTT::TaskContext*, bool) (in
/usr/lib/liborocos-rtt-corba-gnulinux.so.1.4.0)
==18442== by 0x46AE610:
RTT::Corba::ControlTaskServer::CreateServer(RTT::TaskContext*, bool) (in
/usr/lib/liborocos-rtt-corba-gnulinux.so.1.4.0)
==18442== by 0x46A19F6: Orocos_ControlTask_i::getPeer(char const*) (in
/usr/lib/liborocos-rtt-corba-gnulinux.so.1.4.0)
==18442== by 0x47317ED: POA_RTT::Corba::getPeer_ControlTask::execute() (in
/usr/lib/liborocos-rtt-corba-gnulinux.so.1.4.0)
==18442== by 0x4AFE9D2: TAO::Upcall_Wrapper::upcall(TAO_ServerRequest&,
TAO::Argument* const*, unsigned, TAO::Upcall_Command&, void*, CORBA::TypeCode*
const*, unsigned) (in /usr/lib/libTAO_PortableServer.so.1.4.7)
==18442== by 0x472F2BF:
POA_RTT::Corba::ControlTask::getPeer_skel(TAO_ServerRequest&, void*, void*) (in
/usr/lib/liborocos-rtt-corba-gnulinux.so.1.4.0)
==18442== by 0x4AFAF6D:
TAO_ServantBase::synchronous_upcall_dispatch(TAO_ServerRequest&, void*, void*)
(in /usr/lib/libTAO_PortableServer.so.1.4.7)
==18442== by 0x472B55A:
POA_RTT::Corba::ControlTask::_dispatch(TAO_ServerRequest&, void*) (in
/usr/lib/liborocos-rtt-corba-gnulinux.so.1.4.0)
==18442== by 0x4AC75CA: TAO_Object_Adapter::dispatch_servant(TAO::ObjectKey
const&, TAO_ServerRequest&, TAO_Pseudo_Out_T TAO_Pseudo_Var_T >) (in /usr/lib/libTAO_PortableServer.so.1.4.7)
==18442== by 0x4AC81C2: TAO_Object_Adapter::dispatch(TAO::ObjectKey&,
TAO_ServerRequest&, TAO_Pseudo_Out_T TAO_Pseudo_Var_T >) (in /usr/lib/libTAO_PortableServer.so.1.4.7)
==18442== by 0x4BFB1D2: TAO_Adapter_Registry::dispatch(TAO::ObjectKey&,
TAO_ServerRequest&, TAO_Pseudo_Out_T TAO_Pseudo_Var_T >) (in /usr/lib/libTAO.so.1.4.7)
==18442==

The object_to_string() code in the CORBA layer looks ok, and the resulting IOR
string from that function is correct. This is possibly a bug in our TAO version
(Debian Etch).