armagetron for dapper drake

[Z-Man]

AFAIK, there is no x86_64 binary for 0.3.0 at all. I tested the 32 bit exe today on our work machines that are running 32 bit Drake Kubuntu without problems. Of course, lacking root rights, I installed it into ~/.local/, maybe that's the crucial difference? Try installing as normal user without sudo, after uninstalling the previous stuff ("sudo armagetronad-uninstall" should take care of that).

Anyway, it would be nice to know what gdb thinks the error is; "illegal instruction" is a bit cryptic. Just do

Code: Select all

gdb armagetronad
r
<wait for crash>
backtrace

and send in the output.

Oh wait, what CPU do you have exactly? It may be that the binary is "optimized" for the wrong type and uses special AMD instructions. I'm not passing any special flags to GCC during the build, IIRC, but maybe something tickled down from the gentoo ebuild configuration.

And just a clarification: newbie and anjori, does 0.2.8.2.1 work for you?

[ed]

I had 0.2.8.2 running without problems on my laptop running Kubuntu with the i686 package.
I upgraded to 0.3, again without problems (except lacking sound, may be a simple fix here, haven't tried to find it). I still get around 5fps since it's software rendering, but it works.
That's on a P3 733.

[anjori]

AFAIK, there is no x86_64 binary for 0.3.0 at all. I tested the 32 bit exe today on our work machines that are running 32 bit Drake Kubuntu without problems. Of course, lacking root rights, I installed it into ~/.local/, maybe that's the crucial difference? Try installing as normal user without sudo, after uninstalling the previous stuff ("sudo armagetronad-uninstall" should take care of that).

I tried reinstalling Kubuntu in hopes that it would fix the illegal instruction error and some other annoyances I had with the last Kubuntu install, but no luck. I chose the local install without using sudo this time, which made no difference.

Anyway, it would be nice to know what gdb thinks the error is; "illegal instruction" is a bit cryptic. Just do

Code: Select all

gdb armagetronad
r
<wait for crash>
backtrace

and send in the output.

Code: Select all

---Type <return> to continue, or q <return> to quit---
Program received signal SIGILL, Illegal instruction.
[Switching to Thread -1215973696 (LWP 18615)]
0xb7ed4d98 in png_handle_gAMA () from /home/anjori/.local/lib/libSDL_image-1.2.so.0
(gdb) backtrace
#0  0xb7ed4d98 in png_handle_gAMA () from /home/anjori/.local/lib/libSDL_image-1.2.so.0
#1  0xb7ec1061 in png_read_info () from /home/anjori/.local/lib/libSDL_image-1.2.so.0
#2  0xb7eab243 in IMG_LoadPNG_RW () from /home/anjori/.local/lib/libSDL_image-1.2.so.0
#3  0xb7ea7ca4 in IMG_LoadTyped_RW () from /home/anjori/.local/lib/libSDL_image-1.2.so.0
#4  0xb7ea7ac2 in IMG_Load () from /home/anjori/.local/lib/libSDL_image-1.2.so.0
#5  0x081652fc in std::basic_iostream<char, std::char_traits<char> >::~basic_iostream ()
#6  0x08050a06 in ?? ()
#7  0x08051590 in ?? ()
#8  0xb7b02ea2 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#9  0x0804edd1 in ?? ()

Oh wait, what CPU do you have exactly? It may be that the binary is "optimized" for the wrong type and uses special AMD instructions. I'm not passing any special flags to GCC during the build, IIRC, but maybe something tickled down from the gentoo ebuild configuration.

AMD Athlon 1333.

And just a clarification: newbie and anjori, does 0.2.8.2.1 work for you?

It is 0.2.8.2.1 that I'm getting the error with. Though I also tried 0.3 to see if I'd have any better luck with that, and same error.

Unfortunately, that's about the extent of any debugging I can do as this is on my spare (test) machine and I'll be going back to a Debian pure install shortly. I fail to see what all the hype with (K)ubuntu is about as I've had nothing but problems and every time I fix one issue, another arises. So, time to scratch it off the list and move on.

[Lucifer]

Heh, Kubuntu finally pushed me off. I've gone over to Gentoo. If you're willing to spend some time building your system, I'd recommend it, but you need a functional linux partition while you're building your gentoo partition so you can still do Real Work.

[Z-Man]

Ah, the error comes from the SDL_Image library that autopackage installed for you. Things may work better if you remove it ( "package list" to get the list of installed packages and "package remove <package name>") and along with, possibly, libpng, both for your local user and the systemwide install that's possibly lingering around, and install it via you distribution's method. "sudo apt-get install libpng libsdl-image1.2" should do the trick.

[anjori]

Thanks, Z. That did the trick. Though isn't the purpose of Autopackage to take care of such dependencies and make installation simple?

Also, I'm not sure if it's a problem with Autopackage itself or the Armagetron binary, but every time I tried to uninstall the package it would bitch about a missing file (I forget what now) and all but hang my system; 'top' showed a process called "dirisempty" eating up an unhealthy amount of CPU and memory. On the plus side, my frustrations with Autopackage caused me to take another shot at compiling Arma from source, which turned out to be a success.