lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

I'm sure the basic idea could be implemented on Emacs; scite-debug
comes with a version of clidebug that has a 'gdb mode'. But the
single-stepping requires a little dance between clidebug and
scite-debug; the first finds the address and enters debug_break; the
second has to set the temporary breakpoint, but only if it's in valid
C source. No doubt that's possible in Emacs (very few things are
impossible with it ;)) but it would require some elisp work. That
thought gives me a headache. Perhaps there is already some mechanism
to hook into break events and do some custom operation?

Alternatively, think layering; if the scite-debug part could be
separated out as a standalone Lua process, then Emacs could probably
consume the output directly.

Emacs <-> luagdb <-> GDB <-> clidebug

steve d.

On Tue, Mar 11, 2008 at 11:46 AM, Leo Razoumov <> wrote:
> On 3/11/08, steve donovan <> wrote:
>  > Hi all,
>  >
>  >
>  >
>  >
>  >
>  >  There are some notes at:
>  >
>  >
>  >
>  >  The big feature of this release is integrated C/Lua debugging. In
>  >  particular, it is possible to single-step from Lua code to C extension
>  >  code.  To do this, scite-debug runs the clidebug Lua debugger _within_
>  >  a GDB session - this version of clidebug has a 'gdb mode' where it
>  >  understands a subset of GDB commands and generates appropriate -f
>  >  style file:line breaks.
>  > [...]
> >  Give it a whack; some parts are still brittle, but I'm interested in
>  >  where it breaks!
>  >
>  >  steve d.
>  >
>  Steve,
>  awesome achievement!! It is, indeed, a very useful feature.
>  Can scitedebug run stand alone or it requires SciTE/Scintilla ?
>  I am (still) an emacs user and am not familiar with SciTE at all.
>  --Leo--