ltrace

Two implementations

ltrace.lua pure lua

src/ltrace.c pure C, see src/test.lua, easy to use, but without table dumping, just call ltrace.traceback()

Description

How To Debug With Lua, Lots of print?

We don't need print() any more!

Instead of debug.traceback(), this lib gives you more infomations of every lua call stack frame.

lua Support

luajit Support(with param names for function output)

In C++ or Java, you just use

try {
	// statements
} catch(e) {
	// statements
}

while in Lua, you need xpcall like this:

function TryFunc()
	-- statement
end

function CatchFunc(err)
	-- statement
	print(err)
	print(debug.traceback())
end

xpcall(TryFunc, CatchFunc)

in CatchFunc, we just call debug.traceback() to get stackframe to locate your mistake.

ltrace.getfulltrace() will show you every variable(name and value) of each frame(with function name, filename and linenum) in lua call stack

Output Format

Variables show in each frame are sorted by declaration order.

If you are using luajit or lua 5.2 later, param names will be showed in brackets. See Example

frameidx @filepath.lua:linenum in <functionName()>
	local_variable_name1:variable_value
	local_variable_name2:variable_value
	...

How To Use?

local ltrace = require "ltrace"

function errordump(errstr)
	io.stderr:write(errstr .. "\n")
end

function main()
	-- do call
end

xpcall(main, function(err)
	errordump(err)
	errordump(ltrace.getfulltrace())
end)

Example

test.lua

this is a sample of err catching dumping (use luajit or lua 5.2 or later)