The International Simutrans Forum

Hi,

I tried to run Simutrans Experimental 7.3 on Linux (Ubuntu) but I keep getting a segfault.

gdb output:
Program received signal SIGSEGV, Segmentation fault.
0x0000000000613063 in display_ddd_box_clip(short, short, short, short, unsigned short, unsigned short) ()

I tried the i386 and amd6 versions, tried deleting the settings.xml, nothing works.

I use the build from http://www.43-1.org/~simutrans/simutrans-exp/i386/

Anyone managed to run STE on Linux ?

To whoever does the automatic builds, could you perhaps build with DEBUG=1 to get us debug information in the official builds of experimental?

Ahh - I had taken debugging information out on the "official" builds because I wanted a clean release build for people to use that is as optimised as possible, without (for example) lots of ****ert checks slowing things down. Indeed, I specifically use the #IFDEF DEBUG flag to give additional (and not so user friendly) information in the GUI on occasions. Certainly, the Windows version is compiled as a "release" build in MSVC++.

What, I think, we could really do with is having nightly builds for Experimental on all platforms: the nightly builds would have the debugging information turned on, and the release builds would have it turned off.

As to the original poster's query - if I recall correctly, I think that there are 64-bit Linux builds of Standard. Perhaps some testing could be done of the Standard version to check whether this is a problem there, too? If it is, perhaps this topic needs to be moved out of the "Experimental" section of the board.

Could one of the people with AMD64, where experimental is failing, try the "Standard" 64-bit build, so we know whether the problem is here or there?

I have a little request too - any chance the names of the downloads could be made more informative? Ideal would be a name like "simutrans-experimental-amd64-2010-05-02" (same for the experimental Pak btw, the download filename is without version number). That way it would be much easier to track which version people used when encountering problems.

Starting with the next build (simutrans|makeobj)-exp-latest should redirect to the files including a date.  This way the browser should save the files that way as well.

[snip] As to the crashes - a backtrace would indeed be useful, as it would be good to get a 64-bit version running in case people have problems running the 32-bit version (although note that there is no performance advantage to the 64-bit version as I understand it: if Simutrans is using anywhere near 4Gb of memory, something is wrong in any case).

I should also be interested in your experiences of the stability of the 32-bit version on 64-bit Linux, to see whether a 64-bit version really is needed at all.

Then I'm really confused, how can it be that the auto-build segfaults but my own build works? What exact settings (and GCC and library versions) are used to make the autobuild, I could try rebuilding with those to try and reduce the number of possible causes.

Good idea but I don't have ccache installed so that can't be it

No, no, the autobuild might have ccache installed, and that may be causing breakage there.

it failed at dataobj/einstellungen.o

Code: [Select]

dataobj/einstellungen.cc:979: error: cast from ‘const char*’ to ‘uint32’ loses precision

changed that to uint64, that compiles

update
couldn't resist trying a bit and caused this:
Code:

Code: [Select]

Program received signal SIGSEGV, Segmentation fault.
0x000000000059e72c in vector_tpl<koord>::remove_at (this=0x7fffffffb910, 
    pos=0, preserve_order=false)
    at boden/wege/../../dataobj/../tpl/vector_tpl.h:213
213					data[pos] = data[count-1];	

error is reproduceable, just loaded my savegame (the one i uploaded previously), and waited.