Fix and improve the Lua Debugger

As a Roblox developer, it is currently too hard to debug my code.

Unfixed Bugs

  • Sometimes a yield call will cause a breakpoint to stop working when stepping into it, meaning it does not resume the breakpoint script screen. I don’t know how to reproduce this. It seems that the calls which cause this to occur are consistent, but the types of calls I’m not sure about. I can make some DataStore requests that work with breakpoints and others that don’t, for example. wait() calls don’t seem to ever cause this behavior.
  • Breakpoints crash Studio seemingly randomly even without yield calls. They have to be the singular primary cause of my crashes. Don’t know how to reproduce this. Some crashes seem inconsistent (the same breakpoints at the same code won’t always crash).

New Functionality Requests

The Lua Debugger seems like it was written and forgotten about. This is a shame because it is tremendously useful. It greatly speeds up the debugging process, and print() calls are a subadequate replacement.

I suggest that breakpoints be made compatible both client-side and server-side in all testing modes. Currently, they only work in Run and Accurate Play Solo modes server-side; never in Test Server and never

My Old Bug’s Fix Remains Dead

The breakpoint bug I reported many months ago apparently has a fix, but was never made live. Because of this particular bug remaining unpatched, a breakpoint on this code crashes Studio consistently:

for i = 1, 10 do end

And when on this code, causes an “attempt to yield across metamethod/C-call boundary” error:

for i, v in pairs({"a", "b"}) do print(i, v) end

I am running Windows 10.


This topic was automatically closed after 1 minute. New replies are no longer allowed.