BUG in CORBA_ORB_object_to_string, created bad IOR, .....

[Sergiu Gavrila <sg itdesign de>]

Hello all,
I have o problem using the ORBit CORBA_ORB_object_to_string method. I am 
working on a PHP extension that uses ORBit to access a CORBA application 
server (Visibroker). All is ok (or almost :-)) until I use 
CORBA_ORB_object_to_string. This gives me a warning (BUG in 
CORBA_ORB_object_to_string, created bad IOR, .....), and if I try to 
access the returned string, I get a Speicherzugriffsfehler (memory 
access error). There is no exception, just the warning, and a bad string.
I'm using a cvs version, actually a tarball : ORBit-20000902. I also 
tried ORBit-0.5.7 but the obit-idl compiler does not likes my idl files 
(if I run it, it takes all the available memory, and never stops).
Can somebody help me? Is there a newer  version? Where? (I can't access 
the www.labs.redhat.com/orbit from where I think I got this version, my 
browser just times out!)
Maybe a patch?

Many thanks,
 Sergiu Gavrila

The code is below:

    char* cursor;   
    cursor = CORBA_ORB_object_to_string(orb,la, &ev);

    if(ev._major != CORBA_NO_EXCEPTION) {
      mylog("CORBA_ORB_object_to_string exception!");
      return NULL;
     }
    return cursor;

la is a reference (LA_Listenansicht la) to CORBA object implemented with 
Visibroker (C++). I have no problems accessing this object, but if I try 
to call CORBA_ORB_object_to_string .......

Running the code that contains this,  results in:
-------------------
** WARNING **: IOP_TAG_MULTIPLE_COMPONENTS decoding needs finishing

** WARNING **: IOP_TAG_MULTIPLE_COMPONENTS decoding needs finishing

** WARNING **: IOP_TAG_MULTIPLE_COMPONENTS decoding needs finishing

** WARNING **: Skipping tag 1

** WARNING **: Unknown tag 0x400a4e64

** WARNING **: Bug in CORBA_ORB_object_to_string, created bad IOR 
`IOR:010000001900000049444c3a4c412f4c697374656e616e73696368743a312e3000000000020000000000000048000000010100000e0000003139322e3136382e312e313838000dc92c00000000564201000000115642526f6f74504f412f626f615f74700020202000000002323820203a9e3d0c000d97bd'

Speicherzugriffsfehler
------------------------