How are you contructing/connecting your proxy? it looks like you are just using an invalid proxy object/pointer..


2008/10/17 <>
Thanks for the tip Geoff.  I performed the backtrace and
got the following:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb797e6c0 (LWP 7789)]
0x0804a673 in PlayerCc::ClientProxy::GetVar<double> ()
(gdb) bt
#0  0x0804a673 in PlayerCc::ClientProxy::GetVar<double> ()
#1  0x0804a6ae in PlayerCc::Position2dProxy::GetXPos ()
#2  0x08049bd8 in Robot::getCurrentCoords ()
#3  0x08049fb4 in main ()

Does this mean I'm supplying ClientProxy::GetVar with the
wrong data?  I searched through the forums and found a
similar issue with the laser proxy, and tried to implement
a similar solution:

while(lp->GetCount() == 0)

Reading in laser data did not make a difference, but I
can't find a way to read in Position2d data without
causing another segmentation error.  I tried the

while(pos->GetXPos() == 0)

But simply get caught in an infinite loop, or do not enter
the loop at all.  The same applies regardless of which
member function I choose for the while test.  I would like
to get a return from pos but can't see any member
functions that aren't going to get me in the same
situation; is there any way I can avoid getting into this

That is, assuming that the solution to this segmentation
fault with the position2d proxy is the same as for the
laser proxy :-)

Many thanks


This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
Playerstage-users mailing list

This email is intended for the addressee only and may contain privileged and/or confidential information