Linux64 bit support

[Keith Smith]

wow, linux is going to be so much fun to support.

I'll have to build a version with more debugging to find out where it's falling over.

[Keith Smith]

I wonder if some of this is related to the new system ID check. I'll build a version that has debugging around that step and see if that's doing it.

[jpoirier]

It looks like your GCC compiler (v 4.8.2) is a version behind the latest 4.8.3 release. There's also a 4.9.1 release as well.

$ readelf -p .comment lin.xpl

String dump of section '.comment':
[ 0] GCC: (Ubuntu 4.8.2-19ubuntu1) 4.8.2

[edit]
You can install GCC 4.9.1 on Ubuntu via:
$ sudo add-apt-repository ppa:ubuntu-toolchain-r/test
$ sudo apt-get update
$ sudo apt-get install gcc-4.9
$ sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.9 20
$ sudo update-alternatives --config gcc

gcc will now link to gcc-4.9 in /usr/bin but you can still get to version 4.8 explicitly via gcc-4.8


-joe

[theluckyone17]

wow, linux is going to be so much fun to support.

For what it's worth, we appreciate it greatly. My Windows XP10 install is suffering from a huge delay on start up. Haven't bothered to track it down quite yet, what with my Linux install being available (and it runs faster with better graphics to boot).

If there's any information or assistance we can provide, just holler.

[wmburns]

Just a short note to say that I completed a new test mule Unbuntu Linux build.

Running

• Unbuntu 14.04 LTS 64 bit
• NVidia
• X-Plane 10.31
• PilotEdge
• Saitek Yoke, dual throttle, rudder pedals
• Saitek Radio panel supported via XsaitekPanels.
• Audio via analog speaker/mic built into the mother board.
• additional Unbuntu installed packages include Nvidia-311 and "openal1". Very modest OS changes. Latest 10.31 no longer needs "libudev"

I was able to logon to PilotEdge and complete a short flight KSNA-KSAN. I still have some joystick/button configuration to re-do but the simulator worked well.

I'm planning on running the Linux X-Plane as much as possible to test how stable it is. Will update as I learn more.

Congratulations Keith! PilotEdge now has a 64 bit Linux client. Something the Vatsim community has been requesting for a very long time. Seems like this may open a new possible customer base and reason to consider PilotEdge.

FYI, I was not able to get the 32 bit Unbuntu Linux version to work with X-Plane 10.31. I assuming that it would be a benefit to test further so I will keep that test system around.

Thanks.

[theluckyone17]

Just out of curiousity, wmburns, what are you running for audio equipment? I'm running the XP output through my onboard card, and Pilotedge through a USB headset.

I'll see if I can download an Ubuntu 14.04 live CD later and compare software versions...

Edit: If I did more than skim through wmburns' post, I'd know he has a single sound card. Ah, well. I'll try running the plugin via a single sound card, and see if that changes anything.

[sanjiv]

Gave it a try on Ubuntu 14.04 64bit with X plane 10.31 with similar results as reported by injunear and theluckyone17.

Running valgrind confirms memory leak somewhere within setVoiceChannel ().

Code: Select all

**3137** *** strcpy_chk: buffer overflow detected ***: program terminated
==3137==    at 0x4C2D9EC: ??? (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==3137==    by 0x4C31A73: __strcpy_chk (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==3137==    by 0x23549FD8: setVoiceChannel (in /home1/sanjiv/X-Plane 10/Resources/plugins/PilotEdge/64/lin.xpl)
==3137==    by 0x2354C02B: connect(char const*, char const*, char const*, char const*, char const*, char const*) (in /home1/sanjiv/X-Plane 10/Resources/plugins/PilotEdge/64/lin.xpl)
==3137==    by 0x2354CFEF: ConnectWidgetHandler(int, void*, long, long) (in /home1/sanjiv/X-Plane 10/Resources/plugins/PilotEdge/64/lin.xpl)
==3137==    by 0x228F5178: XPSendMessageToWidget (in /home1/sanjiv/X-Plane 10/Resources/plugins/XPWidgets_64.so)
==3137==    by 0x228F523E: XPSendMessageToWidget (in /home1/sanjiv/X-Plane 10/Resources/plugins/XPWidgets_64.so)
==3137==    by 0x228EEF15: XPButton(int, void*, long, long) (in /home1/sanjiv/X-Plane 10/Resources/plugins/XPWidgets_64.so)
==3137==    by 0x228F5178: XPSendMessageToWidget (in /home1/sanjiv/X-Plane 10/Resources/plugins/XPWidgets_64.so)
==3137==    by 0x228F64A3: XPWidgetMouse(void*, int, int, int, void*) (in /home1/sanjiv/X-Plane 10/Resources/plugins/XPWidgets_64.so)
==3137==    by 0x226AA83C: XPLMDisplayMouseClickHook(int, int, int) (in /home1/sanjiv/X-Plane 10/Resources/plugins/XPLM_64.so)
==3137==    by 0x226ACAD3: XPLMMouseClickHook (in /home1/sanjiv/X-Plane 10/Resources/plugins/XPLM_64.so)

[eddiedee]

Joe, also what distro/arch and xplane10 version you're using? I am using it on Kubuntu 14.04 64bit and have used it flawlessly for numerous hours now.

The kernel version is 3.13.0-37-generic 64-bit and the distro is Elementary OS Freya, which is Ubuntu based. X-Plane runs fine with the PilotEdge plugin loaded, it only crashes when I try to connect to the PilotEdge network.

[edit] ...and X-Plane 10.30.

-joe

Hi All - Just signed-up thanks to Linux 64 bit support. I have a similar issue with crash upon network connect, however I think have found a very odd work-around/repeatable bug.

When connecting to the network with a six digit callsign, e.g. "N629JG" PilotEdge crashes upon connection. However when connecting with a five digit callsign, e.g. "N17HE" PE connects to the network without incident. I have attached a BT and Log.txt. This issue is totally repeatable on my machine, with different A/C etc.

Ubuntu 14.04 LTS 64bit
XP10.25
PE 1.1.1

Thanks,
Ed

[jpoirier]

Joe, also what distro/arch and xplane10 version you're using? I am using it on Kubuntu 14.04 64bit and have used it flawlessly for numerous hours now.

The kernel version is 3.13.0-37-generic 64-bit and the distro is Elementary OS Freya, which is Ubuntu based. X-Plane runs fine with the PilotEdge plugin loaded, it only crashes when I try to connect to the PilotEdge network.

[edit] ...and X-Plane 10.30.

-joe

Hi All - Just signed-up thanks to Linux 64 bit support. I have a similar issue with crash upon network connect, however I think have found a very odd work-around/repeatable bug.

When connecting to the network with a six digit callsign, e.g. "N629JG" PilotEdge crashes upon connection. However when connecting with a five digit callsign, e.g. "N17HE" PE connects to the network without incident. I have attached a BT and Log.txt. This issue is totally repeatable on my machine, with different A/C etc.

Ubuntu 14.04 LTS 64bit
XP10.25
PE 1.1.1

Thanks,
Ed

I can confirm that the shorter "N" number fixed my "crash at connect" problem. Nice catch!

-joe

[sanjiv]

Indeed the five character callsign works like a charm.
Thanks for the workaround eddiedee.