Question 1

How do I set up MobDebug for remote debugging?

Accepted Answer

Add 'require("mobdebug").start()' to your script and run 'lua -e "require('mobdebug').listen()"' to start the server. Ensure LuaSocket is installed and paths are configured correctly to avoid common issues.

Question 2

What's the difference between MobDebug and Lua's built-in debug library?

Accepted Answer

MobDebug offers remote debugging, cross-platform support, and IDE integration, whereas Lua's built-in debug library is local and lower-level. MobDebug is better for distributed environments but adds complexity and overhead.

Question 3

How to debug coroutines in MobDebug?

Accepted Answer

Use 'require('mobdebug').on()' inside the coroutine or 'require('mobdebug').coro()' globally. Note that C API coroutines require explicit 'on()' calls, and breakpoints may not trigger by default.

Question 4

Why are my breakpoints not working in MobDebug?

Accepted Answer

Common causes include path mismatches, case sensitivity on different OSes, coroutine issues, or infrequent socket checks. Check the troubleshooting guide for solutions like using absolute paths or adjusting checkcount.

Question 5

How to integrate MobDebug with nginx or OpenResty?

Accepted Answer

MobDebug provides specific support for nginx/OpenResty; refer to the examples and ensure Lua modules are loaded correctly. It may require embedding the debugger in Lua code within nginx configurations.

Question 6

Does MobDebug add significant performance overhead?

Accepted Answer

Yes, due to periodic socket checks (every 200 statements by default). You can reduce this by adjusting checkcount, but it may affect breakpoint responsiveness in low-statement scenarios.

MobDebug

What is MobDebug?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions