Debugging Lua Code

wiki

Lua comes with debugger interface, so that users can write their own monitoring code (e.g., for a debugger, tracer, or profiler) through the Lua Debug library [1]. Some examples are below.

• Inline / Command line debuggers
  • [RemDebug] - remote debugger in Kepler
  • [clidebugger] (5.1) - a simple portable Lua command line debugger, inspired by RemDebug? but without its remote facilities
  • [ldb] by RiciLake (broken link?)
    • A few versions may be found here: [2]+[3], [4] (also search "rici ldb" on http://lua-users.org/lists/lua-l/ )
  • [ctrace] (5.0/5.1) - a tool for tracing Lua API calls.
  • [xdbLua] (5.1) - a simple Lua command line debugger for Windows.
  • [LuaInterface-debugger] (5.1) - a debugger extension for LuaInterface.
  • [Rldb] - remote lua debugger via sockets. written in C
  • [Ldb] much older debugger by Tomás Guisasola

• Graphical debuggers
  • See LuaIntegratedDevelopmentEnvironments.
  • For SciTE, see SciteDebug (No watch window in debugging).
  • [Software Verification Lua Memory Validator]
  • [Software Verification Lua Bug Validator]
  • Decoda is Graphical debugger with remote debugging support[Decoda] (Debugging does not work "from the box")
  • [GRLD] - graphical remote lua debugger with source code, free of charge for non-commercial use. Works with lua-jit too. (Does not work "from the box". Very buggy.)
  • [akdebugger] Debugger and editor for Lua. Plugin for Eclipse.

• Other
  • [StackTracePlus] -- provides enhaced stack traces