Re: [Flightgear-devel] Networking doesn't work (for me at least)

2003-01-01 Thread Curtis L. Olson
--network-olk was never really finished, and the code hasn't been
touched in probalby over a year.  With other changes that have gone
on, it's not surprising that this code doesn't work.

Regards,

Curt.


Tommy McDaniel writes:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 I recompiled FlightGear yesterday with the option
 --with-network-olk (since I didn't do that the first
 time), but it doesn't seem to work. When I run fgfs
 --enable-network-olk I don't get a Network menu or
 any other kind of indication that networking is up.
 Further, when I throw in the option --net-hud the
 program has a segmentation violation the moment I try
 to switch the HUD on. I got a backtrace, and here's
 the part that matters:
 
 Refreshing timestamps for -122.375 37.5625
 scheduling needed tiles for -122.358 37.6117
 
 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 1024 (LWP 20388)]
 net_hud_update () at net_hud.cxx:81
 81other = head-next;
 (gdb) backtrace
 #0  net_hud_update () at net_hud.cxx:81
 #1  0x080ef1f4 in fgUpdateHUD (x_start=-172.307709,
 y_start=0, x_end=812.307678, y_end=480) at
 hud.cxx:1172
 #2  0x080eeca9 in fgUpdateHUD () at hud.cxx:1048
 #3  0x080e8875 in fgCockpitUpdate () at
 cockpit.cxx:713
 #4  0x08050a63 in fgRenderFrame () at main.cxx:854
 #5  0x080527fa in fgMainLoop () at main.cxx:1265
 #6  0x40090845 in idleWait () from
 /usr/lib/libglut.so.3
 #7  0x0805700a in main (argc=3, argv=0xb804) at
 main.cxx:1823
 #8  0x403963c1 in __libc_start_main () from
 /lib/libc.so.6
 
 It sure looks like we're dereferencing another NULL
 pointer. Just in case there was some kind of unusual
 funkiness with configure, I erased all installed
 FlightGear binaries and recompiled again with
 --with-network-olk=yes, but I get the same result.
 This almost seems like an error on my part somewhere,
 but I don't know where it would be. I just tried
 running FlightGear again with --httpd=3000 and then
 again with --telnet=3000, in case that made a
 difference, but it still crashes the moment I try to
 turn on the HUD. Does anyone know what's going on
 here?
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.2.1 (GNU/Linux)
 
 iD8DBQE+C0ISVB8FYP9YqDcRAruxAJ9Szv/dUjhy8qzXeX6mIjJPZNrWkgCfS/GG
 vbzrZ3eKE7Q2XGI12ftmTM4=
 =HQYA
 -END PGP SIGNATURE-
 
 
 __
 Do you Yahoo!?
 New DSL Internet Access from SBC  Yahoo!
 http://sbc.yahoo.com
 
 ___
 Flightgear-devel mailing list
 [EMAIL PROTECTED]
 http://mail.flightgear.org/mailman/listinfo/flightgear-devel

-- 
Curtis Olson   IVLab / HumanFIRST Program   FlightGear Project
Twin Cities[EMAIL PROTECTED]  [EMAIL PROTECTED]
Minnesota  http://www.menet.umn.edu/~curt   http://www.flightgear.org

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



[Flightgear-devel] Networking doesn't work (for me at least)

2002-12-27 Thread Tommy McDaniel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I recompiled FlightGear yesterday with the option
--with-network-olk (since I didn't do that the first
time), but it doesn't seem to work. When I run fgfs
--enable-network-olk I don't get a Network menu or
any other kind of indication that networking is up.
Further, when I throw in the option --net-hud the
program has a segmentation violation the moment I try
to switch the HUD on. I got a backtrace, and here's
the part that matters:

Refreshing timestamps for -122.375 37.5625
scheduling needed tiles for -122.358 37.6117

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 20388)]
net_hud_update () at net_hud.cxx:81
81other = head-next;
(gdb) backtrace
#0  net_hud_update () at net_hud.cxx:81
#1  0x080ef1f4 in fgUpdateHUD (x_start=-172.307709,
y_start=0, x_end=812.307678, y_end=480) at
hud.cxx:1172
#2  0x080eeca9 in fgUpdateHUD () at hud.cxx:1048
#3  0x080e8875 in fgCockpitUpdate () at
cockpit.cxx:713
#4  0x08050a63 in fgRenderFrame () at main.cxx:854
#5  0x080527fa in fgMainLoop () at main.cxx:1265
#6  0x40090845 in idleWait () from
/usr/lib/libglut.so.3
#7  0x0805700a in main (argc=3, argv=0xb804) at
main.cxx:1823
#8  0x403963c1 in __libc_start_main () from
/lib/libc.so.6

It sure looks like we're dereferencing another NULL
pointer. Just in case there was some kind of unusual
funkiness with configure, I erased all installed
FlightGear binaries and recompiled again with
--with-network-olk=yes, but I get the same result.
This almost seems like an error on my part somewhere,
but I don't know where it would be. I just tried
running FlightGear again with --httpd=3000 and then
again with --telnet=3000, in case that made a
difference, but it still crashes the moment I try to
turn on the HUD. Does anyone know what's going on
here?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+C0ISVB8FYP9YqDcRAruxAJ9Szv/dUjhy8qzXeX6mIjJPZNrWkgCfS/GG
vbzrZ3eKE7Q2XGI12ftmTM4=
=HQYA
-END PGP SIGNATURE-


__
Do you Yahoo!?
New DSL Internet Access from SBC  Yahoo!
http://sbc.yahoo.com

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel