Spring RTS Engine

Spring crashed 2 times during the battle.
Both times - when commander blowed.
But some commanders were blowed without crash.
Infolog attached.

please install the debug-symbols for spring (spring-dbg) + use spring non-mt.

thank you! spring-dbg was installed. I will still try to use spring-mt and I will update this thread if this bug will be reproduced.

Lot's of people use mt because it rocks. I love beautiful(smooth) mid game joins.

abma wrote:please install the debug-symbols for spring (spring-dbg) + use spring non-mt.

Just to clarify. Is "spring-dbg" a client side debug build? I've been asked to use one due to an ongoing issue I'm experiencing. So it would be useful. Thank you!

spring-dbg (ubuntu-package) are the debug-symbols...

abma wrote:spring-dbg (ubuntu-package) are the debug-symbols...

I don't understand it too.
So wikipedia says: http://en.wikipedia.org/wiki/Debug_symbol
"Sometimes the symbolic information is compiled together with the module's binary file, or distributed in separate file". Looks like in this situation "debug-symbols" are distributed in separate file.

But I still has no idea how this file will be linked to binary to provide more info during crash. I just decided to look at infolog next time to see the differences.

meh, sorry i forgot, the debug-symbols are only useful if you use gdb.

so, to get a more useful stacktrace when it crashed: don't press ok on the "Spring has crashed" dialog box.

to attach gdb to the running spring, you've to first get the pid: here it is 4439, then attach gdb to the running process:
then with "bt" or "bt full" you get a similar (but much more useful) output like in infolog.txt. without the debug symbols, no line info is shown.

ty, abma! Interesting quest! :-D

abma wrote:meh, sorry i forgot, the debug-symbols are only useful if you use gdb.

so, to get a more useful stacktrace when it crashed: don't press ok on the "Spring has crashed" dialog box.

to attach gdb to the running spring, you've to first get the pid:

Code: Select all

ps aux|grep spring
abma      2586 10.6  6.9 1058856 282028 ?      Sl   13:13  10:49 /usr/lib/firefox-10.0.2/firefox http://springrts.com/phpbb/viewtopic.php?f=11&t=27804&p=516598&e=516598
abma      4439 14.8  6.0 480956 245584 pts/0   S+   14:54   0:09 spring
abma      4455  0.4  0.5 278152 20932 pts/0    S+   14:54   0:00 zenity --title Spring crashed? --error --text Spring has crashed:?Segmentation fault (SIGSEGV).??A stacktrace has been written to:?  /var/tmp/home/.spring/infolog.txt?
abma      4482  0.0  0.0  10764   872 pts/1    S+   14:55   0:00 grep spring

here it is 4439, then attach gdb to the running process:

Code: Select all

sudo gdb -p 4439

then with "bt" or "bt full" you get a similar (but much more useful) output like in infolog.txt. without the debug symbols, no line info is shown.

I don't understand what you are saying here.. Could u make this more clear (possibly with a link to the stuff I'd need)? I have been having irregular crashes throughout the last versions which don't give any(!) info in the infolog so maybe this method gives some insight.

this only works on linux, i guess you're on windows?

abma wrote:this only works on linux, i guess you're on windows?

Yes. Are there solutions for windows to get more info on a crash if it doesnt get jotted down in infolog?

The cause of this crash has been identified. Thanks for reporting.

zerver wrote:The cause of this crash has been identified. Thanks for reporting.

Super! Thank you zerver for mt version!

Try this
http://springfiles.com/spring/game-inst ... cutable-v2

zerver, what to do for linux users like me? If you can provide instructions how to checkout to this version, I will test it.

Today I see a lot of people crashing when commander blowed. I hope it will be really fixed in 88.0

checkout 87.0 and then

git cherry-pick 029369c
git cherry-pick d304846

A bit offtopic, but anyone tested how much debug version slowdown everything?

wolas wrote:A bit offtopic, but anyone tested how much debug version slowdown everything?

You mean a regular debug build? That is unplayably slow.

Stupid post warning!
I m not coder so this might sound stupid. Yeah I mean debug build which was named spring-dbg in the ubuntu repos is it regular debug build? I guess no?

I know that normal debug build you can see every variable and so on so this one is -> unplayable slow, but spring-dbg package is something different if not whats the point in recommending it if you cant even go to such point where it will crash?
Stupid post warning!

I am not sure about linux, but if it is something like this:

http://springrts.com/dl/buildbot/default/master/87.0/

spring-dbg is simply the debug symbols for spring. You use it to translate the addresses in a stack trace and help you guess in which source files the bug is located.