Spring RTS Engine

Hi,

There is so many reasons Spring can crash i start to call it like that, "Crash".

Between Spring itselfs, the AI, the maps, a problem in a 3D0 file, etc., it's really hard sometimes to understand why the game crash.

Actually, i'm even in a position i can't understand why the game crash on my mod.

i wanted to know if it's possible to have a better log where we have the reason why my mod crash. And the worst thing is it don't always crash. Just really often.

I know unitsync.log & infolog.txt

the stacktrace can tell you exactly what it was doing when it crashed

Thank for you fast answer, but what is stacktrace ?

check your infolog.txt

Infolog.txt don't give the crash reason.

Go to lobby
/j #buildserv
post whole infolog to pastebin.ca
!translate file=http://pastebin.ca/1398154 in #buildserv
Enjoy.

Tried :

[15:18:24] * BuildServ * Downloading stacktrace...
[15:18:27] * BuildServ * [OK] Downloaded at 96.2 KB/s
[15:18:27] * BuildServ * Detecting build parameters...
[15:18:27] * BuildServ * [WARNING] Unable to find detailed version in infolog, autodetection disabled
[15:18:27] * BuildServ * Checking debug data availability...
[15:18:27] * BuildServ * [OK]
[15:18:27] * BuildServ * Parsing stacktrace...
[15:18:27] * BuildServ * [ERROR] Unable to find translatable stacktrace in file

Tried in text mode, in raw. Tried in copy and in download file.

If there is a stacktrace it goes at the end of the infolog; that's why kburts said to look there. http://pastebin.ca/1398243 doesn't have one, so please describe the crash in detail. Was there an error box? Did spring hang? etc.

In fact, the game simply close. As if "killed" by the system.
No message, no error box, nothing.

Do you want to continue discussing, or just post the infolog somewhere

sorry ?

Your infolog.txt, post it somewhere (pastebin .e.g) and give link.

lurker wrote:http://pastebin.ca/1398243

lurker wrote:http://pastebin.ca/1398243

lurker wrote:http://pastebin.ca/1398243

I found something by chance : When a unit (The "Hyene") is hit, after a few hits the game crashe.
The unit is far to be destroyed, don't answer (it's non-armed), and the COB file don't have line for "hit", "wounded" and so on...

in linux, spring crashing doesn't print the stacktrace even if debug symbols are builtin, maybe fixing that won't be too hard considering there are quite few stacktrace dump lib/code snippets available around

patches welcome, useful stuff is IMVU's CallStack e.g.

useful stuff is IMVU's CallStack e.g.

... is what ?

Brain Damage wrote:spring crashing doesn't print the stacktrace

That's okay, but it doens't print anything when it catches an error? That's a rather important bit of info, that there was an error, and that it was caught.

I don't think it catches errors at all on Linux.

(At least the errors we're talking about here; ie. segfaults)