Re: Getting local variable debug info from within a nested function.

["Matthew Armstrong" <turkeypotpie@...>]

> Sure. See the debug. library.
Ahhh ok, I see it now, there is a special function for upvalues.  Thanks.

> If there are specific features you feel it lacks, please let me know.
My debug routine aims to do something similar to ldb, albeit on a smaller scale.  This works pretty well, but being able to set breaks, and easily step in-and-out is very useful in some situations.  This is one area where an IDE's graphical version is much easier to use than a console driven app, imo.

On 6/11/07, Rici Lake <lua@ricilake.net> wrote:

On 11-Jun-07, at 3:28 PM, Matthew Armstrong wrote:

> With regards to my original question, is there a way to get the
> upvalue's value? If ldb can do it, I'm assuming there is a way.

Sure. See the debug. library.

> I don't find this to be at all bloated, and find it vastly more useful
> than all of lua's IDEs combined. Maybe I've been weaned on using
> debuggers over the years, but having breakpoints with variables really
> does make my life easier. I actually talked a bit with the LuaEclipse
> guys, and they are certainly thinking about something like this, but
> like so many other things, it's "in the works."

I'm not sure what you mean by "breakpoints with variables". ldb lets
you look at all the visible variables at the current execution point
(with
the show command), or to evaluate an _expression_ using the visible
variables. It does not yet have watchpoints, but I'm planning on adding
them; all the infrastructure is there to do it.

ldb is not a visual debugger, of course, but I'm trying to make it
modular enough that it could be managed from an IDE.

If there are specific features you feel it lacks, please let me
know.