I am far enough into learning Ruby so that I need to track down problems
that can't be solved just by examining the source. So far I have been
using the built-in debugger that comes with Ruby, which works fine, but
has all the drawbacks of the Perl debugger - i.e., it is command line
driven and slow.
I prefer the command line on most stuff except for debugging. There just
isn't enough room for data to fit on the screen and what is there scrolls
off fast. Piping it to an editor or file captures everything, but that
requires another operation to inspect and is always after-the-fact.
Perl has a great little tool in the ptkdb debugger that is a gui and
lets you grasp a much bigger part of the problem you are trying to solve
and in real time, so to speak. Alas, while TK works with Ruby pretty good,
the debug tool doesn't.
Question. Is there a more sophisticated troubleshooting tool for Ruby
available yet (for Linux)? I been googling without much luck so far,
although on a 24k dialup it may be several months before I get to the
bottom of the list. (In this part of the country you have to pay AT&T
extra for broadband - that is to say, 56k dialup).
I am far enough into learning Ruby so that I need to track down problems
that can't be solved just by examining the source. So far I have been
using the built-in debugger that comes with Ruby, which works fine, but
has all the drawbacks of the Perl debugger - i.e., it is command line
driven and slow.
I prefer the command line on most stuff except for debugging. There just
isn't enough room for data to fit on the screen and what is there scrolls
off fast. Piping it to an editor or file captures everything, but that
requires another operation to inspect and is always after-the-fact.
Perl has a great little tool in the ptkdb debugger that is a gui and
lets you grasp a much bigger part of the problem you are trying to solve
and in real time, so to speak. Alas, while TK works with Ruby pretty good,
the debug tool doesn't.
Question. Is there a more sophisticated troubleshooting tool for Ruby
available yet (for Linux)? I been googling without much luck so far,
although on a 24k dialup it may be several months before I get to the
bottom of the list. (In this part of the country you have to pay AT&T
extra for broadband - that is to say, 56k dialup).
I suppose apropos of nothing in particular I'll mention that the
version of ruby-debug in SVN (tentatively scheduled as the version
0.9.4) has a number of changes, many of towards the command-line
aspect which make this more gdb-like. I've been working on user manual
and guide which right now (again tentatively) can be found at ruby-debug . Be warned however if you follow
that link or look a that guide that there are a number of features in
it that are not in 0.9.3.
···
On Aug 12, 11:45 pm, "Wayne E. Seguin" <wayneeseg...@gmail.com> wrote:
On Aug 12, 2007, at 22:34 , Jim Phillips wrote:
> I am far enough into learning Ruby so that I need to track down
> problems
> that can't be solved just by examining the source. So far I have been
> using the built-in debugger that comes with Ruby, which works fine,
> but
> has all the drawbacks of the Perl debugger - i.e., it is command line
> driven and slow.
> I prefer the command line on most stuff except for debugging. There
> just
> isn't enough room for data to fit on the screen and what is there
> scrolls
> off fast. Piping it to an editor or file captures everything, but
> that
> requires another operation to inspect and is always after-the-fact.
> Perl has a great little tool in the ptkdb debugger that is a gui and
> lets you grasp a much bigger part of the problem you are trying to
> solve
> and in real time, so to speak. Alas, while TK works with Ruby
> pretty good,
> the debug tool doesn't.
> Question. Is there a more sophisticated troubleshooting tool for Ruby
> available yet (for Linux)? I been googling without much luck so far,
> although on a 24k dialup it may be several months before I get to the
> bottom of the list. (In this part of the country you have to pay AT&T
> extra for broadband - that is to say, 56k dialup).
I think that radrails (eclipse) had plans on integrating ruby-debug, so that might work.
RadRails is based on RDT. And RDT is developed by Chris Williams and debugger was developed for quite long time by Markus Barchfeld (not sure how it is now). On the work of Markus was based - more than half year ago (do not exactly remember); debug-commons[1] project on RybyForge where we are cooperating (RDT and NetBeans currently ) on the common debugger layers (= non-frontend) which are IDE, interpreter and language (not only for Java based frontend) independent.
So definitely RDT has already support for ruby-debug as well as everybody who will base their frontend on the debug-commons project. We just have too much plans with debug-commons and not enough people
