When FlightGear is compiled with a hardened gcc (gcc-3.3.6 in this
case), fgfs fails at startup in the following way:
opening file: /usr/share/games/FlightGear/Navaids/carrier_nav.dat
/usr/share/games/FlightGear/Navaids/TACAN_freq.dat
RenderTexture Error: Couldn't find a suitable pixel format.
Initialising callsign using 'Aircraft/c172p/Models/c172p.xml'
fgfs: stack smashing attack in function virtual void FGJSBsim::update(double)()
Aborted
For completeness a backtrace:
$ gdb fgfs
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /usr/games/bin/fgfs
[Thread debugging using libthread_db enabled]
[New Thread -1219197264 (LWP 21176)]
__driCreateNewScreen - succeeded
opening file: /usr/share/games/FlightGear/Navaids/carrier_nav.dat
/usr/share/games/FlightGear/Navaids/TACAN_freq.dat
[New Thread -1422353488 (LWP 21179)]
RenderTexture Error: Couldn't find a suitable pixel format.
[New Thread -1430746192 (LWP 21180)]
Initialising callsign using 'Aircraft/c172p/Models/c172p.xml'
fgfs: stack smashing attack in function virtual void FGJSBsim::update(double)()
Program received signal SIGABRT, Aborted.
[Switching to Thread -1219197264 (LWP 21176)]
0xffffe410 in __kernel_vsyscall ()
Current language: auto; currently c
(gdb) bt
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb78fadc6 in kill () at string2.h:1000
#2 0xb78e7690 in __stack_smash_handler (
func=0x85fac20 "virtual void FGJSBsim::update(double)", damaged=0) at
ssp.c:153
#3 0x08157890 in FGJSBsim::update (this=0xaed32b8, dt=0) at JSBSim.cxx:496
#4 0x00000000 in ?? ()
(gdb)
When compiled with a vanilla gcc-3.3.6, fgfs flies fine (at least
for the short while I've used it so far).
Benno
_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d
