i tried to compile Spring from the GIT Repo.
Compilation succeded, but when i start spring with
,for Example, Balanced Annihilation and "Empty Script" or Commanders,
spring always hangs up in a endless Loop allocation up to about 3G of RAM,
ending in the Error "std::bad_alloc".
It's the same Result, no matter which Startscript(Random Enemies, Commanders,...) and Modification i have selected.
I checked out Version 4afe06b7eb425914f7a0dc87 from the GIT Repo.
I'm running a 64 Bit Gentoo.
(2.6.27-rc5-git1 #1 SMP PREEMPT Mon Sep 1 22:10:38 CEST 2008 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ AuthenticAMD GNU/Linux)
And i'm using Boost-1.35.0-r2.
Can i set spring to be more verbose, so i can get a Clou why spring behaves like this. Or is this a common Problem?
While writing this new Topic, i tried to include some Console Messages. So i restarted Spring with "LC_ALL="C" gdb spring -w" to get english Messages.
Now i don't get the Error anymore! Spring starts with Path Calculation and starts up.
With the Command "gdb spring -w", i get the following Messages from spring and the Backtrace from gdb:
Code: Select all
spring: /usr/include/boost/thread/pthread/mutex.hpp:50: void boost::mutex::lock(): Zusicherung »!pthread_mutex_lock(&m)« nicht erfüllt.
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x42097950 (LWP 747)]
0x00007f7d6836b165 in raise () from /lib/libc.so.6
(gdb) bt
#0 0x00007f7d6836b165 in raise () from /lib/libc.so.6
#1 0x00007f7d6836c4de in abort () from /lib/libc.so.6
#2 0x00007f7d6836449f in __assert_fail () from /lib/libc.so.6
#3 0x0000000000a36800 in ?? ()
#4 0x0000000000a36878 in ?? ()
#5 0x0000000000a368b6 in ?? ()
#6 0x0000000000c247b7 in ?? ()
#7 0x0000000000639c88 in _start ()
Thanks in advance,
Kaot