On Feb 14, 2013, at 12:27 PM, Joshua Jensen <josh.jjensen@gmail.com> wrote:
One of the best features of this is that it (theoretically... I've never looked myself) would not cause any additional garbage to be created for Lua to collect. When you are working within constrained memory heaps, I want to debug my Lua code in the same state that it would ship in. Most remote debuggers like mobdebug end up loading additional stuff into the Lua state and causing additional memory usage.
Sure, but the reason you may have a "constrained memory heap" is because your Lua-using program is on another system, like in an embedded appliance. LDT and ZBS let you access that remotely - i.e., true remote debugging, rather than just local other-process debugging. To get true remote debugging, you have to make some change in that appliance's code somewhere/somehow, for example if just to open a socket and run a remote debugger/API protocol to it (e.g., DGBP).
Although I suppose if your remote appliance is actually running Windows you could use Decoda on it remotely and remote-desktop in or whatever. But isn't running Windows contradictory with the notion of a constrained memory heap?
;)
