Ampere K. Hardraade wrote:
Hardware: mainly with ATI cards with open source Radeon driver. Josh and
Mathias have this problem as well:
http://www.mail-archive.com/flightgear-devel%40flightgear.org/msg35812.html
There is one person on the user-list who uses i845 chipset, and I believe
he/she also reports having the same problem.
In Linux, FlightGear (0.9.8 cvs) can start fine under XFree, although with an
error message "RenderTexture Error: Couldn't find a suitable pixel format."
3D Clouds also isn't visible. Under Xorg, FlightGear would crash with a
GLXUnsupportPrivateRequest error at line 495 in RenderTexture.cpp.
Ok, so at a quick glance, probably the logic of detecting/selecting
pbuffer support is broken for some platforms.
Now we just need to find someone that knows something about pbuffers and
maybe this code specifically ...
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-linux"...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(gdb) run
Starting program: /usr/local/FlightGear/bin/fgfs
[Thread debugging using libthread_db enabled]
[New Thread -1220531616 (LWP 2526)]
Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread -1220531616 (LWP 2526)]
0xafdb10a8 in ?? () from /usr/X11R6/lib/modules/dri//r200_dri.so
(gdb) where
#0 0xafdb10a8 in ?? () from /usr/X11R6/lib/modules/dri//r200_dri.so
#1 0x3f800000 in ?? ()
#2 0x3f800000 in ?? ()
#3 0x3f800000 in ?? ()
#4 0x3f800000 in ?? ()
#5 0x00001d80 in ?? () at rul.cxx:35
#6 0x00001f80 in ?? () at rul.cxx:35
#7 0xbffff038 in ?? ()
#8 0xafdb0fd0 in ?? () from /usr/X11R6/lib/modules/dri//r200_dri.so
#9 0xb7744c9c in __malloc_initialize_hook () from /lib/tls/libc.so.6
#10 0xbfffef9c in ?? ()
#11 0x01744898 in ?? () at rul.cxx:35
#12 0x00949494 in ?? () at rul.cxx:35
#13 0x08056780 in main () at basic_string.h:228
(gdb) cont
Continuing.
Disabling HW TCL support
opening file: /usr/local/FlightGear/share/FlightGear/Navaids/carrier_nav.dat
/usr/local/FlightGear/share/FlightGear/Navaids/TACAN_freq.dat
[New Thread -1491719248 (LWP 2529)]
X Error of failed request: GLXUnsupportedPrivateRequest
Major opcode of failed request: 145 (GLX)
Minor opcode of failed request: 16 (X_GLXVendorPrivate)
Serial number of failed request: 30
Current serial number in output stream: 31
Program exited with code 01.
(gdb) where
No stack.
(gdb) quit
This backtrace looks nonsensical ... gdb is confused obviously due to
missing symbols or some memory got stomped on. Did you also build
simgear with -g, since that seems to be where the actual error is
occuring. Hmmm, either gdb is really confused or you didn't build all
the source code with debugging symbols here. Memory locations aren't
generally very helpful, at least not to me....
The GLXUnsupportedPrivateRequest occurs when line 495 of RenderTexture.cpp is
invoked. It also does the samething if line 516 is invoked. To bypass the
problem, one can introduce a "return false;" statement at line 1831.
However, this would cause strange coloring effects to appear:
http://www.students.yorku.ca/~ampere/fgfs-screen-006.jpg
It sounds to me like whoever setup this pbuffer detection code needs to
take some responsibility for it and make sure the logic works on all
platforms. The alternative is to rip out buggy code until it is fixed.
We have to be really careful about half-baked/unfinished code when it is
in the core of the application and is causing crashes for people. If we
yank this code that means we most likely lose clouds and shadows and
probably a few other things, but that is the only alternative if no one
is willing (or able) to support or fix it.
Curt.
--
Curtis Olson http://www.flightgear.org/~curt
HumanFIRST Program http://www.humanfirst.umn.edu/
FlightGear Project http://www.flightgear.org
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d
_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d
