Re: lush debugger?

Hi Ralf,

It depends what you mean by "source-level debugger".
For intepreted code, Lush itself is -- in effect -- its
own source-level debugger. You can insert breakpoints
anywhere in your code: just insert (pause "some message")
anywhere. Whenever execution reaches it, you get a Lush
prompt, in which you can do absolutely anything you want
(print/set variables, call functions, redefine functions,....).
Hitting CTRL-C during execution gives you a debug prompt as well.

There is also a "debug" function, which print a trace of 
evaluations, but I use it pretty rarely.


For compiled code, there is no built-in debugging mechanism at 
the moment. However, since functions can be individually 
compiled and tested in the context of a larger (interpreted)
program, it makes development easier.

It should be possible to rig the Lush compiler so it inserts 
break points, trace statements, etc...

For profiling, you can use Yury Sulsky's recently CVS'ed 
profiler (see lsh/profiler/profile.lsh). It can profile
interpreted and compiled code.

Also, you can always use gdb: Search for 
"Debugging modules with gdb" in the Lush documentation.

  -- Yann


On Saturday 08 October 2005 07:13 pm, Ralf Juengling wrote:
> Hi list,
>
> Am I correct that the lush does not come with a (source level)
> debugger? This is something quite high on my wish list. If
> anybody has a attempted to write one and has a half-baked lush
> debugger sitting on his or her hard drive, please let me know.
>
> Thanks,
> Ralf





-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl