Forum

CS2D

General

Segmentation fault on launch (Antergos)

Forums overview CS2D overview General overview Log in to reply

Segmentation fault on launch (Antergos)

13 replies

Segmentation fault on launch (Antergos)

GeoB99
Moderator Off

Offline

25.06.17 03:25:06 pm

On my Antergos (Arch based distro, 4.11.6-1-ARCH version) box, CS2D fails to launch and throws a segmentation fault (core dumped). I can't judge whether it's an internal bug or my fail setup but I suspect the problem might be caused by certain incompatible libraries in order to run this game.

This is what strace reports the CS2D's behaviour while launching:

Strace output - Pastebin

And additional information from gdb, the backtrace is also included:

gdb output

GNU gdb (GDB) 8.0
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./CS2D/CS2D...(no debugging symbols found)...done.
(gdb) run
Starting program: /home/zxc/CS2D/CS2D 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0xf6e62d9e in ?? () from /usr/lib32/xorg/modules/dri/i965_dri.so
(gdb) bt
#0  0xf6e62d9e in ?? () from /usr/lib32/xorg/modules/dri/i965_dri.so
#1  0xf6e6468a in ?? () from /usr/lib32/xorg/modules/dri/i965_dri.so
#2  0xf6e64917 in ?? () from /usr/lib32/xorg/modules/dri/i965_dri.so
#3  0xf6e649f6 in ?? () from /usr/lib32/xorg/modules/dri/i965_dri.so
#4  0xf6e59435 in ?? () from /usr/lib32/xorg/modules/dri/i965_dri.so
#5  0xf6e43340 in ?? () from /usr/lib32/xorg/modules/dri/i965_dri.so
#6  0xf6bf7450 in ?? () from /usr/lib32/xorg/modules/dri/i965_dri.so
#7  0xf6bdbe01 in ?? () from /usr/lib32/xorg/modules/dri/i965_dri.so
#8  0xf6bf4915 in ?? () from /usr/lib32/xorg/modules/dri/i965_dri.so
#9  0xf6bad86b in ?? () from /usr/lib32/xorg/modules/dri/i965_dri.so
#10 0xf6baf04a in ?? () from /usr/lib32/xorg/modules/dri/i965_dri.so
#11 0x08246222 in ?? ()
#12 0x082464fc in ?? ()
#13 0x08246986 in ?? ()
#14 0x0824bb1f in ?? ()
#15 0x0824b698 in ?? ()
#16 0x08248c33 in ?? ()
#17 0x080fda04 in ?? ()
#18 0x0810a6b5 in ?? ()
#19 0x08106896 in ?? ()
#20 0x080db1e8 in ?? ()
#21 0x080d71d5 in ?? ()
#22 0x0804cdb4 in ?? ()
#23 0xf78cf253 in __libc_start_main () from /usr/lib32/libc.so.6
#24 0x0804ccd1 in ?? ()
(gdb)

And finally, the ldd output. It reports no missing libraries whatsoever and none of them are corrupt as you can see below:

ldd output

$ ldd ./CS2D/CS2D
	linux-gate.so.1 (0xf77d0000)
	libX11.so.6 => /usr/lib32/libX11.so.6 (0xf764e000)
	libXxf86vm.so.1 => /usr/lib32/libXxf86vm.so.1 (0xf7647000)
	libGL.so.1 => /usr/lib32/libGL.so.1 (0xf75e5000)
	libGLU.so.1 => /usr/lib32/libGLU.so.1 (0xf7558000)
	libfreetype.so.6 => /usr/lib32/libfreetype.so.6 (0xf748b000)
	libstdc++.so.6 => /usr/lib32/libstdc++.so.6 (0xf7307000)
	libm.so.6 => /usr/lib32/libm.so.6 (0xf72ab000)
	libgcc_s.so.1 => /usr/lib32/libgcc_s.so.1 (0xf728f000)
	libpthread.so.0 => /usr/lib32/libpthread.so.0 (0xf7271000)
	libc.so.6 => /usr/lib32/libc.so.6 (0xf70b0000)
	libdl.so.2 => /usr/lib32/libdl.so.2 (0xf70a9000)
	libxcb.so.1 => /usr/lib32/libxcb.so.1 (0xf707e000)
	libXext.so.6 => /usr/lib32/libXext.so.6 (0xf7069000)
	libGLX.so.0 => /usr/lib32/libGLX.so.0 (0xf7046000)
	libGLdispatch.so.0 => /usr/lib32/libGLdispatch.so.0 (0xf6fe7000)
	libz.so.1 => /usr/lib32/libz.so.1 (0xf6fce000)
	libbz2.so.1.0 => /usr/lib32/libbz2.so.1.0 (0xf6fbd000)
	libpng16.so.16 => /usr/lib32/libpng16.so.16 (0xf6f7f000)
	libharfbuzz.so.0 => /usr/lib32/libharfbuzz.so.0 (0xf6ef3000)
	/lib/ld-linux.so.2 (0xf77d2000)
	libXau.so.6 => /usr/lib32/libXau.so.6 (0xf6eef000)
	libXdmcp.so.6 => /usr/lib32/libXdmcp.so.6 (0xf6ee8000)
	libglib-2.0.so.0 => /usr/lib32/libglib-2.0.so.0 (0xf6dba000)
	libpcre.so.1 => /usr/lib32/libpcre.so.1 (0xf6d41000)

These are all the debugging info I could bring here. If you guys know a solution to get rid of this I'd be happy.

Re: Segmentation fault on launch (Antergos)

SQ
Moderator Off

Offline

25.06.17 03:35:21 pm

What's your openGL version?

Re: Segmentation fault on launch (Antergos)

GeoB99
Moderator Off

Offline

25.06.17 03:39:34 pm

glxinfo | grep "OpenGL version"

command returns OpenGL version string: 2.1 Mesa 17.1.3 as the current OpenGL version. I guess that shouldn't be a problem.

Re: Segmentation fault on launch (Antergos)

SQ
Moderator Off

Offline

25.06.17 03:43:32 pm

Which audio driver you are using when launching the game?
If this happens after it starts to load files, this might be due to the sound drivers.

Re: Segmentation fault on launch (Antergos)

_Yank
User Off

Offline

25.06.17 03:46:32 pm

I'm not sure but I believe that it's due to the fact that CS2D now uses a more recent version of OpenGL which is not available on most integrated intel GPUs.

Could you try to run an older version and see how it goes (preferably before SQ's updates on the light engine and such) ?

Also, what's your integrated card or CPU ? Do you have any other GPU appart from the integrated one ?

Re: Segmentation fault on launch (Antergos)

GeoB99
Moderator Off

Offline

25.06.17 04:00:09 pm

SQ: I use Pulseaudio as main sound card driver however I doubt it could be caused by that because Ubuntu and its derivatives use Pulseaudio as well and no seg.faults occured (apart that there was no sound).

@ user

_Yank: Got an earlier version of CS2D and same issue occurs. Here's some info about my CPU.

Info

Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    2
Core(s) per socket:    2
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 37
Model name:            Intel(R) Core(TM) i3 CPU       M 370  @ 2.40GHz
Stepping:              5
CPU MHz:               933.000
CPU max MHz:           2399,0000
CPU min MHz:           933,0000
BogoMIPS:              4790.58
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              3072K
NUMA node0 CPU(s):     0-3
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt lahf_lm tpr_shadow vnmi flexpriority ept vpid dtherm arat

As for the GPU, I only have an iGPU which is Intel HD Graphics and this is it. I don't have other GPUs present on my motherboard.

Re: Segmentation fault on launch (Antergos)

SQ
Moderator Off

Offline

25.06.17 04:04:02 pm

Nope, it uses same openGL as 1.0.0.1 version.. and it doesn't load the engine until you join the server.

Also I know that it will crash when using pulse audio when going into "intro menu", so I'm pretty sure that's the problem.

Try running the game with skip intro flag.

Re: Segmentation fault on launch (Antergos)

_Yank
User Off

Offline

25.06.17 04:17:51 pm

SQ: But it relies on new extensions, therefore the reason of OpenGL mode not working on certain iGPU setups on windows. But yeah, that may not be the cause of the problem.

Re: Segmentation fault on launch (Antergos)

SQ
Moderator Off

Offline

25.06.17 04:27:10 pm

I don't use new extensions. The base of new engine was delivered at 1.0.0.1, therefore there are no higher OpenGL requirements (except DirectX)

Re: Segmentation fault on launch (Antergos)

_Yank
User Off

Offline

25.06.17 04:38:22 pm

I don't want to offtopic but the new versions do indeed make use of new GL extensions. On 1.0.0.1, I'm able to use the advanced light and shadow settings but in newer versions I'm not even able to choose them.

Re: Segmentation fault on launch (Antergos)

SQ
Moderator Off

Offline

25.06.17 04:43:29 pm

Oh right, I was wrong. In 1.0.0.2* I built new engine.
On 1.0.0.1 it still used CPU to generate lighting.

Well it requires openGL 1.5 at the very best. I remember using extensions from 2003, so it should work in anyway, try upgrading drivers perhaps.

But lighting is initialized only when running the gameplay for the first time, so the menu should be loaded without any problems.
Of course it checks for the extensions in when initializing the game, so it would prevent you from using it in the first place.

Re: Segmentation fault on launch (Antergos)

GeoB99
Moderator Off

Offline

25.06.17 04:58:30 pm

SQ has written

Try running the game with skip intro flag.

I ran the game without the intro and it is still the same. Begs the question, if Pulseaudio is really of a big problem then why does it happen on Arch based distros and not on other distros such as Ubuntu?

Sure, it will still crash because of other issues like win bug explained there thread

Black screen on Linux however you can bypass it temporarily and you'll see CS2D not crashing. By this matter, I assume there's something wrong in my system but I can't see exactly where...

Re: Segmentation fault on launch (Antergos)

SQ
Moderator Off

Offline

25.06.17 05:05:51 pm

In either way, I don't really want to explain the issue, you won't just get it. It was fixed meanwhile rewriting some core stuff in 1.0.0.4. DC initialized a lot of stuff twice due to command line and config parameters conflict. I need to get Linux to make sure that doesn't happen anymore.

Re: Segmentation fault on launch (Antergos)

_Yank
User Off

Offline

25.06.17 07:11:18 pm

GeoB99: Nothing is wrong with your system, I used to have this problem on my Arch machine but I can't remember how I fixed it.

Somehow I still think it that it is related to the graphics scene. Your gdb backtrace is reporting that the error is related to i965_dri which happens to be the driver module for your intel integrated GPU.