debugging crashing script

[doofus]

Hi guys

In many cases there is a (simple) error in the script and that causes some kind of exception and processing terminates right there. It is silent and I have no idea where the problem is, sometimes a typo other times a nil variable being used when it should not etc.

My way of "debugging" is to have an adequate number of "print" statements so I can tell where the code execution got interrupted and home into the problem line of code. But this is a very slow and cumbersome technique.

Is there a way, an API perhaps. to allow us to see what went wrong?

[MunkDev]

What are you on about? Literally every time a Lua error occurs, you get a popup from the error handler telling you the call stack trace, the line where it broke and which variables were involved.

[jeffy162]

Yeah, but if I'm not mistaken, you have to have Lua (or .lua?) errors enabled to have that happen.

He (she ?) probably doesn't have that enabled.

[Gethe]

Lua errors are disabled by default. While they can be turned on, I would recoomend getting !BugGrabber and BugSack. These will not only turn on Lua errors, but also present much more useful errors than Blizzards built-in tool.

[doofus]

thank you.

for posterity, it is:

/console scriptErrors 1 to display LUA errors
/console scriptErrors 0 to hide LUA errors

[Seerah]

Is this toggle not in the default options window anymore?

[Ammako]

Not since July 18 2016, no.

[jeffy162]

By-the-way, doofus, it's Lua and not LUA. It's the Portuguese word for moon, and not an acronym or abbreviation.

I'm sorry, but that just drive's me up the wall.

[doofus]

Originally Posted by jeffy162 By-the-way, doofus, it's Lua and not LUA. It's the Portuguese word for moon, and not an acronym or abbreviation. I'm sorry, but that just drive's me up the wall.

I just copy'n'paste from the US battle.net forums :-)