Wow - that was so easy, and very useful!
I'm making a LOT of lua calls; I think I might modify ctrace.c to enable/disable tracing during runtime.
On May 23, 2007, at 3:03 AM, Graham Wakefield wrote:
That looks very useful - I will certainly make use of this.
In fact, I traced the panic down to the culprit by narrowing down the cause of the panic function by function. In the end it was a corrupt stack; I didn't however find out what was corrupting the stack, only used a lua_settop() to make it healthy again. I suspect it may be due to coroutines being collected that had not completed, but I'm not sure.
On May 23, 2007, at 2:52 AM, Luiz Henrique de Figueiredo wrote:
The error message I get from a custom panic handler is 'table index is
nil', but no traceback or any other info as to when it happens.