Re: binding to nameserver problem



On Mon, 27 Aug 2001, Sreeji K Das wrote:

> Hi
>
> I'm not having this problem. I'm using ORBit.0.5.8 with CORBA::ORBit
> 0.4.3. I remember seeing this problem, but do not remember in which
> version ! May be u can upgrade to 0.5.8 & test. Is this happening always
> ? I think it used to give a 'segmentation fault', but it's working
> properly now.

I upgraded to 0.5.8, but I got the same result. There is one more thing
that I forgot to mention. When I start my server application, I get this
message:
Use of uninitialized value in subroutine entry at ./echo3-server.pl line 35.

The code before line 35 is:

my $servant = new MyEchoServer;
my $id = $poa->activate_object ($servant);

$poa->_get_the_POAManager()->activate();

my $namingContext = $orb->string_to_object($ior);

my $name = [{id => "Echo", kind => ""}];

$namingContext->bind($name, $servant);

The bind call is in line 35.
BTW, the orbit-name-server does not segfaults, it exits with return
value 1.
				Bye,NAR
-- 
"Beware of bugs in the above code; I have only proved it correct, not
 tried it."





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]