debugger.lua
debugger.lua copied to clipboard
A dependency free, embeddable debugger for Lua in a single file (.lua or .c)
trying to run the debugger_lua.c.lua file from within the embed folder will result in "attempt to index a nil value" errors, which are not obvious, as to why they happen....
I get this error **PANIC: unprotected error in call to Lua API (attempt to index a function value)** inside function dbg_setup() when setting readFunct param, inside function **lua_setfield(lua, -1, "read");**
Previously, the bottom frame was printed.
For example, use `g0` to jump to the bottom of the stack. Trying to jump out of range triggers cmd_trace instead.
I come from a Ruby background and am used to [`pry`](https://github.com/pry/pry) and [`byebug`](https://github.com/deivid-rodriguez/byebug) as my main debuggers, and spent a good 20mins wondering why I couldn't inspect variables with this...
after i curl my request, script just stop run, and no entry to debug
Windows 10 anniversary update added `ENABLE_VIRTUAL_TERMINAL_PROCESSING` flag to console mode, which can be used to enable ANSI color codes. This can be enabled for LuaJIT environment (where FFI is available)....
When inspecting a table, it sometimes has a property whose value is a long string that fills up the terminal. This is often too noisy. If I wanted to see...
It would be great if using `finish` or `next` within a coroutine would avoid triggering the REPL outside that coroutine (unless the coroutine dies). You can always use `step` if...