Geoff the Medio wrote:Hmm. If you've got GL 2.1 and are still getting segfaults before anything gets rendered on a 32-bit machine... I'm not sure what the problem might be. Trying gdb as mentioned earlier might be helpful.
OK, I will try gdb when I have the time.
Geoff the Medio wrote:
It also complains about python 2.5 not being there (true, ubuntu 10.4 has only python 2.6), but seems to continue after noticing that.
That shouldn't be a problem.
Still, I installed python 2.5 from the ubuntu-deadsnakes repo, but the problem persists.
Geoff the Medio wrote:Ah... looking at your log file again, I note that it's dated August 31. I assumed you were getting into the actual game and crashing when rendering the map, not crashing at the start menu. This suggests you're not even writing the log file before the crash happens... And it's possible the log file not being writable is part of the problem. When you installed, did you do so as root, and then immediately run freeorion as root? If so, you might have created a root-owned log file that can't be overwritten by a non-root user. Deleting that and making sure it's writable might help with the crash on the 64-bit system.
I checked that, but I'm pretty sure I installed it as an ordinary user, and the directory listing supports that:
Code: Select all
drwxr-xr-x 4 pallinger pallinger 120 2010-10-12 09:38 .
-rw-r--r-- 1 pallinger pallinger 9075 2010-08-31 12:50 freeoriond.log
-rw-r--r-- 1 pallinger pallinger 23494 2010-08-31 12:50 freeorion.log
-rw-r--r-- 1 pallinger pallinger 4173 2010-10-12 09:38 ogre.log
However, I noticed that only ogre.log was being written. Still, I tried deleting (more precisely moving away) the old log files, and re-running. The result was that only the ogre.log was being recreated. I do not know how the old freeorion log was created at all, maybe the previous version could go as far as to create it... (I will attach ogre.log, it may help...)
Geoff the Medio wrote:Why you also get crashes on the 32-bit system I'm not sure... Is the log file you're quoting for that system actually created when you're running the program now, and definitely not an old log file that can't be overwritten?
Yes, it is created there. Moreover, there are three Impostor.TFBWGKBLLHEOUXDZ.........128.png files that were created during the last run on the 32-bit system (They contain some meteorite textures or sprites or renderings from different angles). Funny thing is that they are not being recreated if I move them away and re-run freeorion, but they are created if I move them away and run freeorion-start --tech-demo (with 512MB RAM).
Also running with --tech-demo is not segfaulting with 512MB RAM, but (after putting up a blank screen and working the CPU hard for a minute) being killed. However, It segfaults (after approximately 10 seconds) if it gets 1024MB RAM.
I will try to run freeorion in debug mode later. Meanwhile, I would appreciate if somebody had an ubuntu-specific build of freeorion, or at least ubuntu builds of all the dependencies.