Aerofly Professional Delux with Fedora 14: stack smashing detected

[JaXXoN]

Dear Aerofly Linux Community,

First of all, thanks very much to the IPACS developers
for porting Aerofly to Linux - I highly appreciate this
effort!

I enjoyed AFPD4 on Fedora 10 for quite some time now
but after recently updating to Fedora 14 I'm running
into a minor issue:

Aerofly will crash when clicking on "Aircraft I",
"Aircraft II" or "Scenary".

This is the error log I get on the console:

*** stack smashing detected ***: ./aerofly terminated
======= Backtrace: =========
/lib/libc.so.6(__fortify_fail+0x4d)[0x32e5dd]
/lib/libc.so.6(-0xff6b3a76)[0x32e58a]
./aerofly[0x804d4e5]
./aerofly[0x804dcda]
./aerofly[0x80605ea]
./aerofly[0x807fea6]
./aerofly[0x80887e5]
[...]
Aborted (core dumped)

A little googeling revealed that the purpose of the
"stack smashing detection" mechanism is to check if
something is written beyond the currently allocated
stack to prevent accidental incorrect stack operations
(by programming misstakes) or intentional code
injection (by viruses). This is a new feature in glibc
that didn't existed in Fedora 10.

I couldn't find any run-time option to disable this
checking, but my understanding is that you can easily
get rid of those "stack smashing detected" messages by
recompiling an application with "-fno-stack-protector".
However, this sounds more like a hot-fix, because the
real cause for the stack corruption will be not addressed.
Since I don't have access to the source code, this isn't
a solution for me, anyway :-)


With some experimenting, I figured out that the
following aircrafts and scenaries are causing the crash:

Aircrafts:
a-380, an2, banjo, baron58, beryll, bf109, caliber90,
cap10, dg100, dromader, eagle, execjet, extra330-s,
funster, geebee-r2, junior, kadett, katana, logo500,
mars, morane505, nh90, piper-j3, r22, raptor90, reiher
salto, seafury, speedcanard, spitfire-mk9, su29,
telemaster, tigermoth

Scenaries:
aspach, augsburg, eggeland, eschenlohe, hahnweide
hammelburg, herrieden, jesenwang, neuburg, unterwoessen
us-ama-muncie, us-golden-gate, us-hodges-hobby,
us-lincoln-sky-knights, us-monument-valley, us-triple-tree,
vohenstrauss

I think these are all aircrafts an scenaries supplied by
the StarFlight add-on packages that come with AFPD.

When removing those aircrafts and scenaries, then
AFPD works fine, again. Means, I basically can use
Aerofly as expected but the aircrafts and scenaries
listed above are not available.


Just in case it might be helpful, this is what I did
to install AFPD:

1. Installed and registered Aerofly on Windows XP using VirtualBox.
When enabling 3D support for VirtualBox and USB pass through
the Game Commander, then Aerofly just works as expected.

2. Created a vfat formated partition and copied aeryfly into it.
Please note that when copying aerofly onto an ext3/4
file system, then several files need to be re-named for
proper function because of case sensitivty of ext3/4.

3. Installed the Aerofly linux executable.
It seems to be sufficient to just copy the "aerofly" binary
taken from "aerofly-linux-v1110721-b2.tar.bz2" into the
aerofly directory. Copying over all files from the tarball
doesn't make any difference concerning the above reported
crashes.

4. Installed udev rule for the Game Commander:

/etc/udev/rules/10-gamecommander.rules:

SUBSYSTEM=="usb", ACTION=="add", \
ATTR{product}=="Ikarus Gamecommander", MODE:="0666"

BTW.: when not using a udev rule but instead manually
changing the permission of the device node corresponding
to the Game Commander after plugging it in (i.e. "chmod
a+rw /dev/bus/usb/001/004"), then Aerofly (or libusb?)
will not detect the device because it only checks the
first two devices per bus (which are hubs on my system).


I would highly appreciate it if the IPACS developers could
look into this issue and potentially find a solution.


Thanks in advance and best regards

Bernhard

[kamereon]

Similar Problem on 64-Bit Ubuntu 10.10

However stack smashing error will only appear if I try to load an aircraft or scene (this used to work until a few weeks ago). If I edit the main.mcf file manually, I can still use all aircrafts an scenes. Even unofficial ones from the internet.

Stack smashing will not appear in 32-Bit version of Ubuntu, though.
Are you running 64-Bit Fedora? If your HDD is big enough for another partition, maybe you could check out 32-Bit Fedora, just to see if my guess is right that this is a problem with the 64-Bit version of AFPD.

[JaXXoN]

If I edit the main.mcf file manually, I can still use all aircrafts an scenes.

Thanks for the tip, but that doesn't work for me: aerofly crashes during startup
before showing the main menu.

Are you running 64-Bit Fedora? If your HDD is big enough for another partition, maybe you could check out 32-Bit Fedora

Thanks for the suggestions - in my first posting, I should have mentioned that I''m using the
32-bit version of F14. I could try with the 64-bit version just to see if that makes any difference.

regards

Bernhard

[JaXXoN]

Hi,

just to let you know, aircraft and scenery selection works fine
with all aircrafts and sceneries when running aerofly in a
Fedora 10 change root from Fedora 14. Means, the system
boots into F14 then I chroot into my old F10 installation. Then
aerofly works mostly as expected (however, sound is missing,
but I guess that could be worked out).

Anyway, this isn't quite the preferred solution, because you always
need to make sure that both installations (F10 and F14) have the
same graphics drivers installed (means, when I update the driver
for F14, then I have to re-do that for F10, as well).

BTW, just ran across this one:
http://www.ipacs.de/forum/showthread...4022#post14022
So it seems to be quite a common issue.

I would highly appreciate it if an aerofly developer could have
a look at this!

regards

Bernhard