Repository navigation
LuaJIT debugging fails to map line information, possibly due to assignment to iter variable #354
Description
I've encountered a problem (originally in PathOfBuilding) where breakpoints display "The source file has no line information." and refuse to work. It seems that this is caused by some sort of Lua 5.5 vs LuaJIT implementation difference, where the former doesn't allow assignment to variables in for-loops.
For example, the following example seems to break the debugger:
local chars = {}
local s = "hello world"
for c in s:gmatch(".") do
c = "test"..c
table.insert(chars, c)
end
print("break")
return s
This is WITH "luaVersion": "luajit",. Running this and attaching a debugger seems to reliably result in a grayed out breakpoint which doesn't work.
Would it be possible to fully support LuaJIT so that something like this does not happen?
Activity
vaisest commentedon Jun 15, 2026
I've been using the extension for a while now with some lines commented out in trackerFactory.js:
// m.arguments.sourceContent = doc.getText();andm.arguments.sourceContent = fs.readFileSync(m.arguments.source.path, 'utf8');.Not sure how relevant this is, but I haven't had any issues. It seems like this extension functions perfectly fine otherwise, so it would be nice if the issue was fixed.
fixed actboy168#354