Debugger stack trace shows wrong line #s

bgrommes

While debugging, I presume the final component of each stack trace line shown is the line # currently executing but if so, it's wrong:

As you can see, it's reporting one line but the currently executing line is entirely other.
At times the reported line # is past the actual end of the method. Here the method only has 16 lines.

Garry

Thanks, good catch. The debugger was showing the line number from the complete source file, while Studio’s editor shows line numbers relative to the current method body. That’s why the call stack could report line 36 when the highlighted editor line was 8.

This should now be fixed in the next release: https://feedback.objo.dev/bug/788

Call-stack line numbers will match the lines shown in the method editor, while Studio will continue using the full source location internally for navigation and debugging.