Re: [FR-devel] Projects status...

[Baptiste Lepilleur]

I know just about nothing about Ruby debugger (I only used it once, but then
I don't like to debug...), even less about how to write a debugger for Ruby.

Concerning the approach, I would start with the one that can provide a
acceptable set of functionnalities in the less time. Fancier implementation
can be added later. At the current time, the project need to get something
out to attract both users and developpers. An acceptable set of
functionnalities for the debug module would be (for me):
- behind able to trace and set breakpoint within the source (very easy to do
with scintilla, see notest on markers in my previous mail).
- dump variable value (this can be a dump on the console to begin, just
provide a simple way for the user
to add a variable to the list of dump)

Other functionnalities like conditional break, source reload... can be added
later.

Baptiste.

----- Original Message -----
From: "Laurent Julliard" <address@hidden>
To: <address@hidden>
Sent: Thursday, May 02, 2002 1:58 PM
Subject: Re: [FR-devel] Projects status...


> Baptiste Lepilleur wrote:
> >     Well, I'm new around here and I'd like to know the status of the
> > following projects:
> >
> > * Debug: I've skimmed over some thread concerning the choice of a
wrapper.
> > Have a choice been made, is there anything (even if it's just some
testing
> > of the wrapping library).
> >
>
> I have appointed myself as the owner of the debugger module. I spent
> sometime thinking about it and so far I see 2 possible approaches:
>
> - The quick and dirty one: use the open3 ruby call to open a
> bidirectinal pipe to ruby debugger process, transform Ui actions into
> debugger command line and analyse the debugger output to properly update
> the freeRIDE UI.
>
> - The right one: augment Hiroshi NAKAMURA's remote debugger so that you
> can drive it through Ruby code. Hiroshi's remote debugger uses dRuby and
> it will be easy to extend. The big advantage of using the remote
> debugger is you can pass Ruby objects back and forth between the
> debugger and the debuggee though making varibale inspection, formatting,
> etc... much easier. The remote debugger is available at:
>
> http://www.jin.gr.jp/~nahi/Ruby/debugger.tar.gz
>
> You may see other approaches yourself. If so I'd be more than happy to
> discuss them on this ML
>
> Laurent
>
>
> _______________________________________________
> Freeride-devel mailing list
> address@hidden
> http://mail.freesoftware.fsf.org/mailman/listinfo/freeride-devel
>