[AddiB]

As the title says, there is a problem with pilot selection in the newest SVN revision build on a 64bit Arch machine.
It crashes immediately after pilot selection (the "hangar" can be seen for a fraction of a second).

I'll attach the fs2_open.log

[attachment deleted by an evil time traveler]

[niffiwan]

That's a bit odd, and the log doesn't really have any clues as to what is causing the crash.

I've just run FSO successfully on my Centos 6 x86-64 PC at work, and I ran it OK on my xubuntu 12.04 x86-64 home PC last night so it might some something specific with the current libs in Arch?

1) Would you be comfortable in grabbing a gdb backtrace from a crash?
2) For reference would you be able to supply your compile options?
3) Ditto for your library versions (i.e. the output from ldd fs2_open_3.7.1)?

[AddiB]

1) How can I get gdb to accept my arguments without failing to load the game?
It simply crashes, telling me the following:

Code: [Select]

Future debug output directed to: /home/adrian/.fs2_open/data/fs2_open.log
[New Thread 0x7ffff0c11700 (LWP 10189)]
[Thread 0x7ffff0c11700 (LWP 10189) exited]
[New Thread 0x7ffff0c11700 (LWP 10190)]
[New Thread 0x7ffff7fba700 (LWP 10191)]
[Thread 0x7ffff7fba700 (LWP 10191) exited]
[Thread 0x7ffff0c11700 (LWP 10190) exited]
[New Thread 0x7ffff0c11700 (LWP 10192)]
[Thread 0x7ffff0c11700 (LWP 10192) exited]
[New Thread 0x7ffff0c11700 (LWP 10193)]
[New Thread 0x7ffff7fba700 (LWP 10194)]
[Thread 0x7ffff7fba700 (LWP 10194) exited]
[Thread 0x7ffff0c11700 (LWP 10193) exited]
[New Thread 0x7ffff0c11700 (LWP 10195)]
[Thread 0x7ffff0c11700 (LWP 10195) exited]
[New Thread 0x7ffff0c11700 (LWP 10196)]
[Thread 0x7ffff0c11700 (LWP 10196) exited]
[New Thread 0x7ffff0c11700 (LWP 10197)]
[Thread 0x7ffff0c11700 (LWP 10197) exited]
[New Thread 0x7ffff0c11700 (LWP 10198)]
[New Thread 0x7ffff7fba700 (LWP 10199)]
[New Thread 0x7fffe7fff700 (LWP 10200)]
ATTENTION: default value of option force_s3tc_enable overridden by environment.
ERROR: " Web cursor bitmap not found.  This is most likely due to one of three reasons: 1) You're running FreeSpace Open from somewhere other than your FreeSpace 2 folder; 2) You've somehow corrupted your FreeSpace 2 installation, e.g. by modifying or removing the retail VP files; 3) You haven't installed FreeSpace 2 at all.  (Note that installing FreeSpace Open does NOT remove the need for a FreeSpace 2 installation.) Number 1 can be fixed by simply moving the FreeSpace Open executable file to the FreeSpace 2 folder.  Numbers 2 and 3 can be fixed by installing or reinstalling FreeSpace 2." at graphics/2d.cpp:705
[Thread 0x7fffe7fff700 (LWP 10200) exited]
AL lib: (EE) alc_cleanup: 1 device not closed
[Thread 0x7ffff0c11700 (LWP 10198) exited]
[Thread 0x7ffff7fbc740 (LWP 10185) exited]
[Inferior 1 (process 10185) exited with code 01]
If I don't pass any arguments it loads the game in fullscreen mode and stops at the crash.
As described in the tutorial I am unable to leave Freespace to get to the debug output.

2) I compiled it with and without the following options:

Code: [Select]

CFLAGS="-O3 -pipe -fomit-frame-pointer -fno-ident" CXXFLAGS="$CFLAGS"The crash happens with both versions.

3) This is the ldd output:

Code: [Select]

ldd '/home/adrian/fs2/fs2_open_3.7.1'
linux-vdso.so.1 (0x00007ffffd3fe000)
libSDL-1.2.so.0 => /usr/lib/libSDL-1.2.so.0 (0x00007f4f07021000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f4f06e03000)
libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x00007f4f06bd6000)
libvorbisfile.so.3 => /usr/lib/libvorbisfile.so.3 (0x00007f4f069cd000)
libtheora.so.0 => /usr/lib/libtheora.so.0 (0x00007f4f0677e000)
libogg.so.0 => /usr/lib/libogg.so.0 (0x00007f4f06577000)
libopenal.so.1 => /usr/lib/libopenal.so.1 (0x00007f4f0631f000)
libGL.so.1 => /usr/lib/libGL.so.1 (0x00007f4f060ba000)
libGLU.so.1 => /usr/lib/libGLU.so.1 (0x00007f4f05e3b000)
libjansson.so.4 => /usr/lib/libjansson.so.4 (0x00007f4f05c2f000)
libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007f4f059fa000)
liblua5.1.so.5.1 => /usr/lib/liblua5.1.so.5.1 (0x00007f4f057cd000)
libm.so.6 => /usr/lib/libm.so.6 (0x00007f4f054c9000)
libjpeg.so.8 => /usr/lib/libjpeg.so.8 (0x00007f4f05274000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f4f05070000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f4f04d65000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f4f04b4f000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f4f047a1000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4f072b9000)
librt.so.1 => /usr/lib/librt.so.1 (0x00007f4f04599000)
libglapi.so.0 => /usr/lib/libglapi.so.0 (0x00007f4f04372000)
libXext.so.6 => /usr/lib/libXext.so.6 (0x00007f4f04160000)
libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x00007f4f03f5d000)
libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00007f4f03d57000)
libX11-xcb.so.1 => /usr/lib/libX11-xcb.so.1 (0x00007f4f03b55000)
libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f4f0381a000)
libxcb-glx.so.0 => /usr/lib/libxcb-glx.so.0 (0x00007f4f03602000)
libxcb-dri2.so.0 => /usr/lib/libxcb-dri2.so.0 (0x00007f4f033fd000)
libxcb-dri3.so.0 => /usr/lib/libxcb-dri3.so.0 (0x00007f4f031fa000)
libxcb-present.so.0 => /usr/lib/libxcb-present.so.0 (0x00007f4f02ff7000)
libxcb-sync.so.1 => /usr/lib/libxcb-sync.so.1 (0x00007f4f02df1000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f4f02bd1000)
libxshmfence.so.1 => /usr/lib/libxshmfence.so.1 (0x00007f4f029ce000)
libXxf86vm.so.1 => /usr/lib/libXxf86vm.so.1 (0x00007f4f027c8000)
libdrm.so.2 => /usr/lib/libdrm.so.2 (0x00007f4f025bc000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007f4f023a6000)
libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f4f021a2000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f4f01f9c000)


[niffiwan]

Thanks for the info.

Compiling with -fomit-frame-pointer will prevent the debugger from being able to get any useful information, so when you compile the debug version of FSO you'll need to remove that compile option.

You can pass options to gbd when you run FSO. Here's an example:

Code: [Select]

$ gdb ./fs2_open_3.7.1_DEBUG_10611
...
(gdb) run -res 1024x768
...

Lastly, this error you received:

Code: [Select]

ERROR: " Web cursor bitmap not found.  This is most likely due to one of three reasons: 1) You're running FreeSpace Open from somewhere other than your FreeSpace 2 folder; 2) You've somehow corrupted your FreeSpace 2 installation, e.g. by modifying or removing the retail VP files; 3) You haven't installed FreeSpace 2 at all.  (Note that installing FreeSpace Open does NOT remove the need for a FreeSpace 2 installation.) Number 1 can be fixed by simply moving the FreeSpace Open executable file to the FreeSpace 2 folder.  Numbers 2 and 3 can be fixed by installing or reinstalling FreeSpace 2." at graphics/2d.cpp:705

It's usually because you are running FSO from outside the assets directory. When FSO starts it expects the current working directory to contain all the VP files. Or (for Linux only) it also looks in ~/.fs2_open. Anyway, so solve that problem simply "cd" to your assets directory before running gdb. (I'm guessing it'll be ~/fs2/)

[AddiB]

Thank you for your help.

Here is the backtrace after the error:

Code: [Select]

(gdb) backtrace
#0  0x00007fffe6f3fb3e in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#1  0x00007fffe6d65f86 in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#2  0x00007fffe6d6617a in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#3  0x00000000004dfce2 in gr_opengl_save_screen ()
    at graphics/gropengl.cpp:1028
#4  0x00000000007bbe1b in popup_do (pi=0x14815c0 <Popup_info>, flags=67175424)
    at popup/popup.cpp:821
#5  0x00000000007bc4a2 in popup (flags=67175424, nchoices=3)
    at popup/popup.cpp:1013
#6  0x00000000005dcb3a in player_tips_popup () at menuui/playermenu.cpp:1348
#7  0x00000000005c4ceb in main_hall_do (frametime=0.0500030518)
    at menuui/mainhallmenu.cpp:863
#8  0x00000000004189fd in game_do_state (state=1)
    at freespace2/freespace.cpp:6546
#9  0x00000000004c5d23 in gameseq_process_events ()
    at gamesequence/gamesequence.cpp:409
#10 0x0000000000419806 in game_main (cmdline=0x2230ae0 "-mod")
    at freespace2/freespace.cpp:7142
#11 0x00000000004199b5 in main (argc=4, argv=0x7fffffffe3e8)
    at freespace2/freespace.cpp:7276

If you need any more logs just tell me. I'll gladly provide them.

[niffiwan]

Thanks for the backtrace. From it I think you can workaround the issue by using a commandline flag:

Code: [Select]

[ -disable_pbo ]            - Disable OpenGL Pixel Buffer Objects

The Intel Linux drivers for the i965 seem to have different behaviour from the nvidia/AMD drivers wrt Pixel Buffer Objects...

[AddiB]

Thank you for your patient and competent help 

The -disable_pbo flag seems to do the trick!