----- Original Message -----
From: "Jon Stockill" <[EMAIL PROTECTED]>
To: "FlightGear developers discussions" <[EMAIL PROTECTED]>
Sent: Saturday, October 09, 2004 3:41 AM
Subject: Re: [Flightgear-devel] Buildiing/running the ATC network test

> OK, I had chance to have a look at configure.in and removed the section
> causing the problem - I've got the binaries built now, all start up ok,
> but the master segfaults when a pilot or controller connects:
> Starting program:
> /archive/Mirror/flightgear/OpenATC/ATC-0.1/src/Master/master
> [Thread debugging using libthread_db enabled]
> [New Thread 16384 (LWP 11705)]
> Socket created - bound to address: IP:Any:29002
> UDP receive buffer size set to 32768.
> UDP send buffer size set to 32768.
> UDP socket non-blocking IO set.  UDP socket initialized.
> Master Server created - listening on port 29002
> ----
> Then you start the client:
> Pilot started - master is at IP:
> Socket created - bound to address: IP:Any:32770
> UDP receive buffer size set to 32768.
> UDP send buffer size set to 32768.
> UDP socket non-blocking IO set.  UDP socket initialized.
> Connecting to master server at IP:
> Client puzzle solved in 147 ms.
> ----
> And the master falls over:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 11705)]
> 0x080a3e68 in ?? ()
> (gdb) bt
> #0  0x080a3e68 in ?? ()
> #1  0x400e0974 in __dynamic_cast (from=0x80a3e68,
>      to=0x807b740 <typeinfo for TNL::Object>, require_public=134723644,
>      address=0x0, sub=0xbfffefb8, subptr=0x4000a490)
>      at ../../gcc-2.95.3/gcc/cp/tinfo2.cc:282
> #2  0x08056613 in TNL::NetConnectionRep::create (
>      name=0xbfffeb80 "MasterServerConnection") at netConnection.cpp:50
> #3  0x0805c458 in TNL::NetInterface::handleConnectRequest (this=0x809a520,
>      [EMAIL PROTECTED], stream=0xbffff030) at netInterface.cpp:762
> #4  0x0805b11f in TNL::NetInterface::processPacket (this=0x809a520,
>      [EMAIL PROTECTED], pStream=0xbffff030) at
> #5  0x0805affb in TNL::NetInterface::checkIncomingPackets (this=0x809a520)
>      at netInterface.cpp:422
> #6  0x08049cc6 in main (argc=1, argv=0xbffff7f4) at main.cpp:667
> (gdb)
Quite honestly, we ( I ) don't fully understand all the internals and
detailed workings of the TNL libraries and protocols. Where it fails is
clear, why is the question? I have had the master node running and have been
able to connect in all four net configs --- internal on the same machine
with, across a LAN with 192.168.xxx.xxx, across the Internet to, or on the same machine using either its LAN or internet IP

ATM I don't have an answer for you and have been unable to duplicate the
problem on my systems. Bummer...
Once I get the server set up for the field test later today, I'll get back
on this problem and try to find an answer for you.

BTW, for those participating in the test later today, you can run multiple
instance of the controllers and pilots which will help to increase the
traffic load on the master server as nodes connect/disconnect and reconnect.
The more, the merrier...

John W.

Flightgear-devel mailing list

Reply via email to