Page 1 of 1
segmentation fault.
Posted: 03 Nov 2007, 07:29
by nir_hp
Hello,
I have compiled taspring under slamd64 (64 bit linux slackware),
when I run a test it quits and gives me "segmentation fault".
why?
what can I do?
Posted: 03 Nov 2007, 15:24
by HAARP
Someone better move this to the Linux forum.
You could try compiling with debug enabled and running it through a debugger (gdb)
See how I did it here:
http://spring.clan-sy.com/phpbb/viewtopic.php?t=12568
Posted: 03 Nov 2007, 15:34
by Tobi
good point, moved to linux
Posted: 04 Nov 2007, 19:57
by nir_hp
Ok
I did it and this is what I get:
Code: Select all
bash-3.1# gdb spring
gdb: Symbol `acs_map' has different size in shared object, consider re-linking
GNU gdb 6.6
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 "x86_64-slamd64-linux"...
Using host libthread_db library "/lib64/libthread_db.so.1".
(gdb) run
Starting program: /usr/local/games/spring
[Thread debugging using libthread_db enabled]
[New Thread 47726499026096 (LWP 3040)]
[New Thread 1082149184 (LWP 3043)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47726499026096 (LWP 3040)]
0x00002b682d2421e8 in _int_malloc () from /lib64/libc.so.6
(gdb)
Any idea?
Posted: 04 Nov 2007, 20:05
by Relative
I've had this exact same problem twice now, on two separate machines. Both times it just magically fixed itself over time. Leaving me with no idea on what the possible root cause for the problem or how it was fixed.
This is my post from the second time it happened:
http://spring.clan-sy.com/phpbb/viewtopic.php?t=12399
Posted: 05 Nov 2007, 13:24
by nir_hp
what do you mean by "fixed itself over time"?
you compiled it and rerun it evry month?
you recompiled it every month?
Re: segmentation fault.
Posted: 07 Feb 2008, 22:51
by nir_hp
Ok,
it solved by reinstalling openal 0.0.8 and not the trunk.
It seems to be a well known problem with intel on board soundcard.