Improved JSL Stack Trace in Log on Error

[DavidLeber]

The current JSL log that is displayed on an error is lacking. Currently, it displays the following:

• What type of error was thrown
• What line threw the error (but not what file the line is in)
• The body of the JSL file that was run (the entire body, even if it is extremely long)
• Sometimes, a highlight in the body of the JSL file that was run indicating the line that threw the error. This does not always work.

It would be more informative to get the following debug information:

• What type of error was thrown
• A stack trace of the calling functions, with details on which line in each calling function threw the error.

There's really very little value in getting a printout of the JSL file with the highlight when you can read through the file yourself and look for the erroring line. It takes up space in the log and makes me scroll past it to see the actual error that was thrown.

[vince_faller]

Even if it weren't nested inside builtin functions, it would be nice if this worked for user defined functions with 1 layer of builtins.  

[Sarah-Sylvestre]

Hi @DavidLeber, thank you for your suggestion! We have captured your request and will take it under consideration.

[hogi]

• What line threw the error (but not what file the line is in)

hm, not always.

I remember cases where the error pointed to a line where a variable was defined.
But the error was caused by a completely different line.

So, it seems there is some logic behind the tracing "where was the variable assigned, this must be the source of error". This kind of logic can be quite misleading ...
Error tracing: JMP tries to "help"