latest sauerbraten release segfaults in linux (fix inside)

by mykilx on 02/14/2006 01:32, 12 messages, last message: 07/21/2006 17:18, 1450 views, last view: 05/02/2024 06:55

This is a known issue. The binary got "windowsified" somehow. If you want to test out mp in sauer grab this binary,
http://cvs.sourceforge.net/viewcvs.py/*checkout*/sauerbraten/sauerbraten/sauerbraten/bin_unix/linux_client?rev=1.118

overwrite the curropted binary in bin_unix, chmod +x and you should be good to go.

PS please disregard the other post, i screwed up on the subject, dang paste buffers ;)

   Board Index   

#1: ..

by mykilx on 02/14/2006 02:24

PPS Thanks a million eihrul.

reply to this message

#2: Re: ..

by Sigi on 02/16/2006 23:44, refers to #1

Thanks so much for this!
I just made a Package for Arch Linux (www.archlinux.org) including this new binary. Keep up the good work!

Cheers Sigi

reply to this message

#3: ..

by celestial on 07/19/2006 05:24

The latest release (6/11) also segfaults in Linux when it's compiled for amd64.
CVS doesn't compile at all. I can't run the 32 bit binary because of SDL issues.

Should I have created a new thread for this? This one is 5 months old, but it seems to describe the same issue...

Thanks.

reply to this message

#4: Re: ..

by MeatROme on 07/19/2006 08:36, refers to #3

CVS is not stable by definition,
it's the latest development _snapshot_ - which might include any number of bugs.

Cube/Cube2 haven't been developed for 64bit architectures (I guess since they're not very common yet).

Other threads have dealt with this issue more directly - so yes this wasn't the /best/ thread you could have chosen;
seg-fault is just a basic "all purpose" message - more helpful information can be found in system logs and ultimately by running the faulty program through a debugger (like gdb).

So far the main response to 64bit problems seems (to me) to have been :
run it in 32bit-compatibility-mode.
If you cannot (for some reason) install the required (SDL) packages for 32bit then I guess you're pretty much out of luck.

You might try donating your AMD64 to the sauerbraten developer team ... I guess you'd find a taker that'd promise to take care of a 64bit overhaul of the code ;)

reply to this message

#5: Re: ..

by Aardappel_ on 07/19/2006 20:46, refers to #3

We have tried to write the code to be 64bit clean, but we can't test because none of the programmers have a 64bit machine.

If you are on AMD64, please help by compiling the sources from the last official release in debug mode, run under GDB or whatever system, and report any crashes with stack traces, and if you can, dumps of whatever variable are used near the crashing point. Post on this thread or anywhere else :)

reply to this message

#6: Re: ..

by neal on 07/20/2006 02:02, refers to #5

Sourceforge prvides a compile farm with 64 bit machines and many more. If you are looking to test on different architectures i suggest you give it a try. Thanks Neal.

reply to this message

#7: Re: ..

by pushplay on 07/20/2006 03:03, refers to #5

I was going to have a new computer by now but then it turned out that Intel's new chipset beats out AMD's. It's been a while since I seriously considered an Intel cpu but it looks like that's the situation. Maybe in a couple months I'll have my new rig.

reply to this message

#8: Re: ..

by Aardappel_ on 07/20/2006 07:54, refers to #6

that's great that I can compile a 64bit version... but I still can't test it.

reply to this message

#9: Re: ..

by rpointon on 07/20/2006 10:49, refers to #5

If your mac developer(s) are using G5 based machines then there are a couple of trivial settings in xcode to build for 64bit (arch ppc64 and enable 64bit maths).

Note, would have to compile SDL for 64bit too... I'll try this if I get time...

reply to this message

#10: Re: ..

by neal on 07/20/2006 11:24, refers to #8

Very true, but you could let the community do the testing. I was just trying to make a friendly suggestion. Neal.

reply to this message

#11: Re: ..

by Aardappel_ on 07/21/2006 08:56, refers to #10

the community can't help unless they are a programmer who knows how to use a debugger. If they can use a debugger I am sure they can type "make" as well.

But yes, the compile farm can be useful for other things.

reply to this message

#12: ..

by celestial on 07/21/2006 17:18

I'd be more than happy to help, if I knew how to do what Aardappel wants us to. I don't know how to use GDB, and I've never done any C++ programming before.

reply to this message

   Board Index