What is a good way to call lua_breakpoint when implementing a debugger?

[JDaance]

I'm adapting my current debugger based on lua_sethook to luau, and I noticed the luau function

void lua_breakpoint(lua_State* L, int funcindex, int line, int enabled)

seems to take a lua function on the stack as argument. My idea then is to save all "whole file"-function references from requiring files in a hash somewhere, and from the filename push the function representing the entire file onto the stack, then call lua_breakpoint. Is this how its supposed to work, kind of? I'm thinking maybe its wisest and easiest to use a lua table for this storage?

[zeux]

Yeah that's correct. If you're doing this from the C code, then using lua_ref is probably the easiest way to store the functions - you can just store top-level functions after luau_load, since lua_breakpoint will find the right sub-function to put a breakpoint into. You'll need to call lua_getref before using lua_breakpoint, eg

lua_getref(L, stored_idx);
lua_breakpoint(L, -1, line, enabled);
lua_pop(L, 1);

[JDaance]

I can confirm this works very well. I create a lua_ref for a table in REGISTRY_INDEX and then lua_refs in that table for every file-function, and then store filename -> refId fields in the table.

[JDaance]

since lua_breakpoint will find the right sub-function to put a breakpoint into

How does this work with functions that are created "on the fly"? I seemed to have trouble registering a breakpoint with a function created by a function, so to speak. Ignore that, mistake on my part. Everything is working as it should.