Re: Hooks, tailcalls and tracing LuaJIT

[Luiz Henrique de Figueiredo <lhf@...>]

> But note that the Lua debug interface is rather brittle, anyway.
> It mixes too many different concerns, it's not designed to be
> extensible, it works at the wrong abstraction level and it's
> incomplete (doesn't report yields, errors). It may work for simple
> tasks, but a full-blown debugger or trace analyzer needs way too
> much guesswork and workarounds. Even setting a simple breakpoint
> is excessively complicated.

We welcome suggestions to improve the debug interface.