For kicks I would like to write a minimalistic GUI interface to the
debugger.
I prefer C++ or C# for GUI applications (this is not to debate here).
What is the best way to establish communication between my GUI and the
default ruby debugger?
As a starting point, I would just like the gui to show the file being
debugged and the current line of execution. The debug commands will be
set in a command window.
Does anyone know of an open source ruby ide w/ debugger which is not
written in ruby?
Arachno IDE is not written in Ruby … I believe it’s written in Eiffel.
Arachno isn’t open source.
Come to that, neither is our IDE (Ruby In Steel).
Currently Arachno has a fast debugger and our free edition has a slow
debugger. Our commercial edition will, however, have a very fast
debugger
and that certainly isn’t written in Ruby. But no, I’m afraid that won’t
be
open source either
The eclipse-based Ruby Development Tools are pretty good, if you can
get beyond the fact that they’re written in Java…
Martin
Maybe I will look at the source for that.
My problem is that I like using gvim for editing. I rarely have
projects over one file.
I usually use -rdebug on the CLI, but I like how a gui debugger gives a
better feel for where the current line of execution is. Also the
mouse-hover for variable values is handy. I don’t need to do editing.
I just want something fast to popup and debug a script.
I guess similar in concept to insight, for gcc/gdb.
Did you write your own debugger(s) for the editor or do you know of a way
to tie into debug.rb?
In the free edition we have a debugger comprising some Ruby and some C#.
Ruby does the evaluation; C# does the Visual Studio stuff (setting and
displaying breakpoints; drag-and-drop watch variables; an integrated
evaluation console; trace-into/over; autos, locals, run-to, call stack
etc.). It’s a pretty decent debugger, I think (then again, I’m biased!),
which lets you debug both Ruby and Rails applications. But, even though
people have told us they find it fast enough, personally, I am still
dissatisfied with the speed (put simply, it’s not as fast as Microsoft’s
C#
or C++ debugger) which is why we decided to create a completeley new
debugger for the commercial release of Ruby In Steel.
The debugger in the commercial edition is dramatically faster and much
more
powerful (we are already using it internally but we still have some work
to
do before it goes out to our beta testers). I’m afraid that we don’t
plan to
reveal too much regarding the implementation details of the commercial
debugger