Crash report -> Code line number

[pmk65]

Is there any way to "translate" the WeBuilder crash report into a code line number?
As I sometimes have a problem tracking down a crashing error, due to the crash report isn't designed for "mortals"

[Aivars]

Unfortunately FastScript doesn't make it easy. The closest thing to finding the problem is to put the suspicious blocks in try..except like so:

Code: Select all

  try {
    B = nil; //make it crash deliberately
    B.SetSize(10, 10);
  } except {
    alert(ExceptionClassName + "\n" + ExceptionMessage);
  }

But it does not give the line number. To get the line number, too, I would have to crack open the FastScript library but that makes upgrading and future maintenance more difficult. Maybe at some point.

[pmk65]

The problem is that I don't know what part of the code it is that is crashing. Im not even sure it's my code as the crashes is not consistent. (It's my most complex plugin to date so it's bound to crash during development.)
It might be a Beta 5 problem that is causing the crashes I get at the moment, but Im not sure. (I don't want to spam you with unnecessary 2018 beta bugreports)

[Aivars]

This wasn't easy but I managed to add code line numbers to crash report without changing the scripting library. In next beta you will be able to see suspected line in the crash report.

stacktrace.png (60.54 KiB) Viewed 3980 times

[pmk65]

GREAT JOB! This is really helpful when writing/debugging plugins..