Error: Recieved Signal 4

Hey, I hope I have enough information to warrant a bug report, but here goes.
I'm running on an old gateway, Intel Pentium 4 2.4GHz CPU running Arch Linux (3.4.6-1 Kernel) and I've been playing 0.6 for a while now without issue. The warsow package in the Arch database was updated today, so naturally I updated and took a look at the changes on the site. I was pretty excited at the prospect of an update, but after the install completed (without incident) I was met with some nondescript errors:

*******************
ERROR: Recieved signal 4

*******************
Error: Recieved signal 4

*sigh*
I downloaded the source and grep'd for the error before realizing it was a Unix signal the program was just heeding. Warsow doesn't seem to be able to get a word in edge-wise before Linux shuts it down with a SigIll, so unfortunately I have no further information to report...
I'm trying to compile from source now instead of using the Arch package (as it was updated just today it is very likely a problem with the PKGBUILD) but I'm not sure what that entails (is there are README I missed? I just invoked `make` in the warsow-1.0 directory... it appears to be compiling fine)

Either some help building from source or an option I've missed somewhere before launching to prevent the error would be greatly appreciated, and again I'm sorry for such sparse info.

Love the game, hope this isn't the end for me (and thanks for keeping the project alive!)

Quick update, after compiling the source myself I get an identical error.

Look at me talking with myself... Just launching the .exe straight from program files works fine. Go figure :v:

Glad to hear the original compiled binary works!

Did you compile your own version from the official SDK or from the arch package build definition? Maybe something's wrong with their build flags? If you're into that, you could get some traces and report your problem to the package maintainer.

hangy wrote:
Glad to hear the original compiled binary works!

Did you compile your own version from the official SDK or from the arch package build definition? Maybe something's wrong with their build flags? If you're into that, you could get some traces and report your problem to the package maintainer.

This is exactly what I need, thank you! I've used abs to get a few packages I needed to make edits to but didn't even think to use it for debugging. The error is identical whether I use the Arch package or download the SDK source and just run make ( am I correct in running the binaries in source/release/? ) but I will definitely build with debugging symbols and try to sort out what's wrong.

Oddly enough the package build for the sdk package was just out of date... the official repository site and git repo show the new version, but the package-manager is still grabbing an old version (0.6). This isn't the case for the warsow-data package though, so I'm sure my local repo listing is up to date. I just grabbed the up to date script and I'm compiling manually, but it's all my poor old computer can take so it may be a while.

Rayjingstorm wrote:
Hey, I hope I have enough information to warrant a bug report, but here goes.
I'm running on an old gateway, Intel Pentium 4 2.4GHz CPU running Arch Linux (3.4.6-1 Kernel) and I've been playing 0.6 for a while now without issue. The warsow package in the Arch database was updated today, so naturally I updated and took a look at the changes on the site. I was pretty excited at the prospect of an update, but after the install completed (without incident) I was met with some nondescript errors:

*******************
ERROR: Recieved signal 4

*******************
Error: Recieved signal 4

*sigh*
I downloaded the source and grep'd for the error before realizing it was a Unix signal the program was just heeding. Warsow doesn't seem to be able to get a word in edge-wise before Linux shuts it down with a SigIll, so unfortunately I have no further information to report...
I'm trying to compile from source now instead of using the Arch package (as it was updated just today it is very likely a problem with the PKGBUILD) but I'm not sure what that entails (is there are README I missed? I just invoked `make` in the warsow-1.0 directory... it appears to be compiling fine)

Either some help building from source or an option I've missed somewhere before launching to prevent the error would be greatly appreciated, and again I'm sorry for such sparse info.

Love the game, hope this isn't the end for me (and thanks for keeping the project alive!)

I'm getting the same error message.

My computer is also older:

P4 3.4GHz
Nvidia GeForce 6800 XT
Linux Mint Debian Edition

I've also been playing Warsow 6 with no problems (other than a low frame rate)
I'm trying to run Warsow 1 with the unified warsow script the same way I run warsow .6.

I don't know how to compile so I haven't tried that. So sorry if my post isn't helpful.

I couldn't find any computer spec requirements. So I just assumed the error was because my system is too old?

I haven't had time to figure this out since last night, but I should have some time tomorrow to keep trying. I compiled with the new PKGBUILD and received the same error. I recompiled again with the recommended settings to preserve debugging symbols and the gnu debugger still bawked that it couldn't find any. If I make any progress I'll post back here.

I have the same error. Ubuntu Server 12.04 32-bit (P4-2.66GHz, 1.8 Gb RAM), precompiled binaries from warsow.net. Very strange, especially knowing that this binary is compiled for 12.04. Some fix? I'll spawn permanent server for community then.
(updated 2012-08-01 17:18:57)

I just realized that I and topicstarter have the same CPU family.

I've got this problem too on my old laptop with an AMD Athlon 64 3000 Processor. It's because warsow 1.0 is compiled with -msse3 but my processor only supports SSE2. Older P4 Processors only support SSE2 as well.

K1ll wrote:
I've got this problem too on my old laptop with an AMD Athlon 64 3000 Processor. It's because warsow 1.0 is compiled with -msse3 but my processor only supports SSE2. Older P4 Processors only support SSE2 as well.

Is there a simple way to revert to SSE2? Does 1.0 actually make use of SSE3 or is it just as simple as changing the -msse3 build flag to -msse2 in the makefile? According to the wikipedia page 13 new instructions were introduced, so I'm assuming one of those 13 is in the binaries and thus causing the SigIll
(updated 2012-08-06 06:34:27)

Thank you K1ll, changing the -msee3 flag (in the sdk Makefile) to -msee2 fixes the problem entirely. I wonder now what the best way to fix this for everyone is? Is there anyway to test for compatibility in the Makefile before compiling with the new instruction set?

Perhaps I spoke a bit too soon. On a race server there weren't problems, but after connecting to any other server I now recieve the same Error: Recieved Signal 4.
Is the dependence upon SSE3 present anywhere beyond the Makefile and Makefile-c++?

I confirm, disabling -msse3 and enabling -msee2 instead produces server binary that runs perfectly. Here comes a pair of questions, why cant i build only server without client? Problem is described here http://www.warsow.net/forum/thread/14047/1.
And as well i'm receiving this message, running the server:

Warning: Game module not in pk3, disabling pure mode
sv_pure_forcemodulepk3 can be used to force the pure system to use a different module

The solution is given here http://www.warsow.net/forum/thread/13083/1 but using this i get Signal 4 again (quite logical though). What to do?
(updated 2012-08-06 15:01:33)

Rayjingstorm wrote:
Does 1.0 actually make use of SSE3

I'm pretty sure it only improves performance.

Rayjingstorm wrote:
Perhaps I spoke a bit too soon. On a race server there weren't problems, but after connecting to any other server I now recieve the same Error: Recieved Signal 4.
Is the dependence upon SSE3 present anywhere beyond the Makefile and Makefile-c++?

xwind wrote:

And as well i'm receiving this message, running the server:

Warning: Game module not in pk3, disabling pure mode
sv_pure_forcemodulepk3 can be used to force the pure system to use a different module

The solution is given here http://www.warsow.net/forum/thread/13083/1 but using this i get Signal 4 again (quite logical though). What to do?

The problem is that the official modules are compiled with -msse3. Unfortunately that means you'll have to ask the warsow devs to compile future versions with -msse2 and wait for the next release.

xwind wrote:

why cant i build only server without client? Problem is described here http://www.warsow.net/forum/thread/14047/1.

Heh the racesow guy who clownfart mentions is me ^^. I'll make a patch for the Makefile problem and post it here later.

Thx, K1ll.

Here's the patch:

diff -ruN a/Makefile b/Makefile
--- a/Makefile  2012-07-18 13:31:25.000000000 +0200
+++ b/Makefile  2012-08-06 20:36:59.721363603 +0200
@@ -488,17 +488,17 @@
 # Building Rules
 ######################################################################################################
 .PHONY: all \
-       client message-client compile-client link-client \
+       client message-client compile-client link-client start-script-client \
        openal message-openal compile-openal link-openal  \
        qf message-qf compile-qf link-qf  \
-       ded message-ded compile-ded link-ded  \
+       ded message-ded compile-ded link-ded start-script-ded \
        game message-game compile-game link-game  \
        cgame message-cgame compile-cgame link-cgame  \
        ui message-ui compile-ui link-ui \
        irc message-irc compile-irc link-irc \
        cin message-cin compile-cin link-cin \
        angelwrap message-angelwrap compile-angelwrap link-angelwrap \
-       tv_server message-tv_server compile-tv_server link-tv_server  \
+       tv_server message-tv_server compile-tv_server link-tv_server start-script-tv_server \
        clean clean-depend clean-client clean-openal clean-qf clean-ded \
        clean-cgame clean-game clean-irc clean-cin clean-angelwrap clean-game clean-tv_server \
        compile

I don't want to hold up progress, but if enough people are affected by the optimization, and if it isn't that much of a boost for those who can use it, it would be nice to still be able to play the game on both my desktop and laptop. If reverting to SSE2 isn't an option I understand, though. Thanks again K1ll.

Every cpu made in last 8 years or so supports SSE3.