[solved, backtracing now]segfault after enabling FPS Manager

[damaltor]

Hi everybody,

i have a problem: playing spring under linux, wich always worked nicely, i wanted to look around in the lua scrips. i enabled FPS manager, wich started telling me that my hardware (geforce 4) doesnt support shadows (wich was not critical, but enerving). i wanted to put it off again, but before i could do, the game crashed without any error message and i was back in lobby.

i wanted to start another game, but it immediately crashed after "creating sky". tried this 3 or 4 times.

i directly started "spring" from console, and it crashed again after loading sky. console output:

Code: Select all

damaltor@damaltorg:~$ spring
Segmentation fault
damaltor@damaltorg:~$ 

rest of infolog.txt:

Code: Select all

...
[      0] Writing path data file...
[      0] Reading estimate path costs
[      0] Analyzing map accessibility [32]
[      0] Block offset 0 of 896 (block-size 32)
[      0] Path cost 0 of 896 (block-size 32)
[      0] Writing path data file...
[      0] Pathing data checksum: c0669c73
[      0] Creating sky

gonna reinstall now, hop that helps.. :/

[Auswaschbar]

Will not work.

Your config is stored somewhere in ~/.spring, you can either deelte it (but all your maps / mods will be lost), or wait for someone who can tell you how you can disable a widget from outside spring.

[lurker]

~/.spring/LuaUI/config

Once you get it off, it would help if you could load spring, turn it on, hopefully crash again, and read what the last thing the widget did was.

[damaltor]

i messed with that config file for quite a while, no success. probably that widget enabled "something" wich now crashes everytime lua loads, i have no idea.

i had to reinstall in the end, deleteing all .spring contents. bad, but i had no other chance (as far as i could see).

despite of this, i could re-enable it to see what it made, wich would end up in reinstalling again (wich is not funny, but this is open source - so if i could help.. why not.)

where can i exactly see what the lua does/did after a crash? is there a special lua.log or sumthing, or do i have to rely on infolog.txt?

[lurker]

Right, you would have wanted the main config in addition to the luaui config. It's not somewhere simple? :/
Just infolog, but that widget announces its actions before making them.

[damaltor]

ok, tried again. it died probably while enabling bumpmapped water.

here is the complete infolog.txt, generated while starting a game of BA 6.81, my side = arm, enemy was LibRAI. game died few seconds after enaling that script.

http://nopaste.com/p/asj9vlG7G

edit: it indeed helped to disable bumpmapped water in springsettings. no need to reinstall -.-

[lurker]

And I heard there's something in the build system that makes spring on linux not give a stack trace outside of debug mode, awesome. Do you have gdb installed?
1. run "gdb spring"
2. type "run"
3. spring will load up, if it pauses in the gdb window hit enter to continue, you should probably do this in windowed mode
4. turn on the widget, wait for a crash
5. type "bt" in gdb and give us the output

It would be nice to know if it crashes in spring or in your video driver, and this will show it.

[damaltor]

there you are. looks like i ought to get some -dbg package, but couldnt find it in repos.

http://nopaste.com/p/aYIKRKD6S