2025-07-21 12:37 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0002608Spring engineGeneralpublic2012-09-03 10:42
Reporterabma 
Assigned TojK 
PrioritynormalSeveritycrashReproducibilityhave not tried
StatusresolvedResolutionfixed 
Product Version 
Target VersionFixed in Version 
Summary0002608: (master) assertion failed in lauxlib.cpp:189
Descriptionspring: /home/abma/dev/spring/master/rts/lib/lua/src/lauxlib.cpp:189: lua_Number luaL_checknumber(lua_State*, int): Assertion `!math::isnan(d)' failed

http://pastebin.com/kqzTvWET

how to handle assertions in lib/lua?

imo a duplicate of this: https://code.google.com/p/zero-k/issues/detail?id=668&colspec=ID%20Type%20Status%20Priority%20Owner%20Summary
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0007231

abma (administrator)

demo triggers assertions, too

~0007232

Kloot (developer)

Last edited: 2011-08-07 17:49

The whole point of the asserts is that Lua devs are forced to handle them (by testing with debug engine builds and _fixing_ their code), not us.

This one happened during a call to str_format (string.format, also shown by the screenshot), which is not fatal in itself but might point to a more serious bug in ZK gadget logic. Therefore it is ZK's problem and responsibility.

~0007233

abma (administrator)

Last edited: 2011-08-07 18:08

hmm, i guess no game-dev uses a debug build...

~0007234

abma (administrator)

Last edited: 2011-08-07 20:13

can we somehow print a message, where these error occured?

a lua-stacktrace would be nice... but i don't know if that can be easily added to the crashhandler. this would require, to print a stacktrace for all lua instances (lua-states?)

~0007235

abma (administrator)

Last edited: 2011-08-08 00:05

https://github.com/spring/spring/tree/lua-stacktrace
it seems to work in one case....
output is for example: http://pastebin.com/k5W0NqXa
this is for tech annihilation


suggestions?

~0007240

jK (developer)

there is no need to write a custom stacktrace function, Lua already got such one: debug.traceback()

~0009162

abma (administrator)

fixed some time ago:

https://github.com/spring/spring/commit/ba10403b
+Notes

-Issue History
Date Modified Username Field Change
2011-08-07 17:17 abma New Issue
2011-08-07 17:17 abma File Added: 20110807_170427_DownCount_v1_0.82+.4.sdf
2011-08-07 17:19 abma Severity minor => crash
2011-08-07 17:19 abma Note Added: 0007231
2011-08-07 17:19 abma Summary (master) assertion in lauxlib.cpp:189 => (master) assertion failed in lauxlib.cpp:189
2011-08-07 17:20 abma Description Updated
2011-08-07 17:47 Kloot Note Added: 0007232
2011-08-07 17:47 Kloot Note Edited: 0007232
2011-08-07 17:48 Kloot Note Edited: 0007232
2011-08-07 17:49 Kloot Note Edited: 0007232
2011-08-07 18:08 abma Note Added: 0007233
2011-08-07 18:08 abma Note Edited: 0007233
2011-08-07 20:12 abma Note Added: 0007234
2011-08-07 20:13 abma Note Edited: 0007234
2011-08-07 23:55 abma Note Added: 0007235
2011-08-08 00:05 abma Note Edited: 0007235
2011-08-10 13:27 jK Note Added: 0007240
2012-09-03 10:42 abma Note Added: 0009162
2012-09-03 10:42 abma Status new => resolved
2012-09-03 10:42 abma Resolution open => fixed
2012-09-03 10:42 abma Assigned To => jK
+Issue History