Stack display on Lua error

[Rob H]

I've started porting LDJ to G4 at last.

I've noticed that when an error occurs you only get told about the line that was in error, and no call stack. :(

[Rob H]

I tried using xpcall() and using debug.traceback in the error handler but that didn't seem to work.

Any chance of a proper stack trace in the next build?

[Ron]

Honestly I have no idea how to go about that. If you know how in Delphi please let me know.

Inside Girder Delphi handles this very well, and I get stack traces but plugins and the like don't give me any info. (sadly)

[Rob H]

It doesn't seem to work as well as it did in Girder 3, even for plain scripting errors. I get no stack trace at all.

[Promixis]

Thats right... the stack is not unwinding.

Ron what changed between lua 4 and 5?

[Ron]

Rob, sorry I misunderstood your original question.

Anyway there seems to be a difference between the way Lua handles the stack, Mike has sent a question to the Lua mailing list to see what we can figure out here.

[Rob H]

Ah, now I understand your initial response!

[Ron]

We have not heard back from the Lua guys yet. That could mean two things,

1. It was a dumb question :(
2. It was a hard question :(

Darn.