Page 1 of 1

Segmentation fault

Posted: 31 Jul 2007, 20:25
by Relative
I just finished building my new PC. After I installed ubuntu and the latest nvidia drivers Spring crashes straight away. It starts, but after I select a script it crashes.

Terminal Output
rutter@stumpy:~$ spring
Using read-write data directory: /home/rutter/.spring/
Using read-only data directory: /usr/share/games/spring/
Using read-only data directory: /usr/lib/spring/
Using script Air combat test
Map: Green Comet Basic.smf
Mod: "Balanced Annihilation V5.5" from BA55.sd7
Segmentation fault (core dumped)
rutter@stumpy:~$
8600 GTS with nvidia drivers installed via envy.

Posted: 31 Jul 2007, 20:27
by Peet
Your computer is named stumpy, and that is awesome.

Did you try the 'commanders' script? the air combat test uses the xta unit names iirc.

Posted: 31 Jul 2007, 20:27
by imbaczek
try

Code: Select all

$ gdb spring
(gdb) run
[crash here]
(gdb) bt
and post it. maybe there will be some hints.

Posted: 31 Jul 2007, 20:31
by Relative
Peet wrote:Your computer is named stumpy, and that is awesome.
.
tis a kick ass name

Commanders has the same result

Code: Select all

rutter@stumpy:/usr/share/games/spring$ gdb spring
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) run
Starting program: /usr/games/spring 
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---bt
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1243642128 (LWP 14708)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
warning: Lowest section in /usr/lib/libicudata.so.36 is .hash at 000000b4
(no debugging symbols found)
Using read-write data directory: /home/rutter/.spring/
Using read-only  data directory: /usr/share/games/spring/
Using read-only  data directory: /usr/lib/spring/
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Error while reading shared library symbols:
Quit
[New Thread -1244144752 (LWP 14835)]
(no debugging symbols found)
Using script Air combat test
Map: Green Comet Basic.smf
Mod: "Balanced Annihilation V5.5" from BA55.sd7

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1243642128 (LWP 14708)]
0xb77a38dc in ?? () from /lib/tls/i686/cmov/libc.so.6
(gdb) 
Spring freezes after that last line.

Posted: 31 Jul 2007, 20:40
by Lippy
How do you know when you've been playing too much spring.

You name your computer after a unit in BA/AA/CA



How do you know when you've been playing FAR too much spring.

When you associate everyday words with units from BA/AA/CA.

Posted: 31 Jul 2007, 21:31
by imbaczek
Relative wrote:[snip]
Spring freezes after that last line.
It's supposed to. After it freezes, type

Code: Select all

bt
in the gdb line and post what comes out of it.

Posted: 31 Jul 2007, 21:37
by Relative

Code: Select all

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1243736336 (LWP 17825)]
0xb778c8dc in ?? () from /lib/tls/i686/cmov/libc.so.6
(gdb) bt
#0  0xb778c8dc in ?? () from /lib/tls/i686/cmov/libc.so.6
Cannot access memory at address 0xbf5c3fcc
O please don't say it's the RAM.

Posted: 31 Jul 2007, 21:41
by imbaczek
it's hard to tell, TBH. unfortunately, this backtrace is not helpful, and the fact that it's repeatable is suggesting a software failure rather than hardware. If the memory address remains the same accross runs, you can be 100% sure that it's a bug somewhere, but I can't even vaguely tell where. (Well, maybe I can: afaik spring runs threads only for networking - therefore the crash may be happening somewhere in the netcode.)

Posted: 31 Jul 2007, 21:43
by Relative
Well I ran it again after rebooting. The same problem, slightly different output:

Code: Select all

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1243871504 (LWP 5802)]
0xb776b8dc in ?? () from /lib/tls/i686/cmov/libc.so.6
(gdb) bt
#0  0xb776b8dc in ?? () from /lib/tls/i686/cmov/libc.so.6
Cannot access memory at address 0xbf41bfdc
(gdb) quit

Code: Select all

[Switching to Thread -1243248912 (LWP 5934)]
0xb78038dc in ?? () from /lib/tls/i686/cmov/libc.so.6
(gdb) 
(gdb) bt
#0  0xb78038dc in ?? () from /lib/tls/i686/cmov/libc.so.6
Cannot access memory at address 0xbf234fdc

Code: Select all

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1243982096 (LWP 6070)]
0xb77508dc in ?? () from /lib/tls/i686/cmov/libc.so.6
(gdb) bt
#0  0xb77508dc in ?? () from /lib/tls/i686/cmov/libc.so.6
Cannot access memory at address 0xbf50efec

Posted: 01 Aug 2007, 01:48
by Neddie
Alright, I'm not sure if you can do this, but get a boot CD of memtest33. Test your RAM using it, should take several hours - I ran it for 36 just to make sure. If it crashes, you either have heat issues or bad RAM sectors. Anyway, that will either give you the cause or rule out the worst case scenarios.

Posted: 01 Aug 2007, 10:04
by Relative
Yeah, I have memtest. I'm planning on doing it a little later today.

Posted: 01 Aug 2007, 11:46
by Pendrokar
No worries RAM has full time warranty!!!

Posted: 01 Aug 2007, 14:07
by Relative
Pendrokar wrote:No worries RAM has full time warranty!!!
Yeah, if anything is wrong I will just RMA it. Memtest is running right now. So far no errors and cooling is fine. My system temp is in the low 30s C.

Posted: 01 Aug 2007, 18:55
by Relative
Well I let it do 6 passes, which took just under five hours and no errors came up. I'm going to be reinstalling ubuntu a little later, so for now I guess this is going to be on hold. Spring works fine under windows, which is good enough for now.

Posted: 01 Aug 2007, 23:08
by Relative
Everything is now resolved. I did a two things, not sure either any of them were the cause. I found that the stock voltage for the RAM on my mobo was 1.8v, but my RAM had a recommended voltage of 2.1v, so I set the BIOS to +0.3v. I also reinstalled ubuntu in case something was wrong with the installation.

Everything works as it did before, thanks for helping me.