Write full LUA call stack in log on critical error
Posted: Wed Jul 09, 2014 8:32 pm
What the title says. Right now there is only little window with point of error, nothing else is provided.
It is frustrating to have refined code, with high amount of different small specialized methods only to find that such code is very hard to debug.
In such code point of original error has little meaning without knowledge of where it was originally called.
Crude pile of code in single method is actually a lot easier to debug.
I'll probable end up wrapping every event/data.lue in the xpcall for now, but at least pcall did not catch engine generated error on "die()" of a destroyed entity.
It is frustrating to have refined code, with high amount of different small specialized methods only to find that such code is very hard to debug.
In such code point of original error has little meaning without knowledge of where it was originally called.
Crude pile of code in single method is actually a lot easier to debug.
I'll probable end up wrapping every event/data.lue in the xpcall for now, but at least pcall did not catch engine generated error on "die()" of a destroyed entity.