Ruby Debugger

Before I start I’d like to say how happy I am for finding this forum,
and the mailing list. I’m very glad to find like-minded Ruby enthusiasts
like you guys!

Right, as you can see from the link below, I have a custom-made IDE, but
it’s got a blank box that I’d like to fill with a debugging tool, but I
can’t find one. I’ve searched google, but still can’t find one that
provides debugging and a runtime debug log. Does anyone know of/use such
a tool, and can provide me a link?

Thanks.

http://img524.imageshack.us/img524/7837/screenshot1pd2.png

Thank you, I’m now looking into ZenTest.

On Wed, Apr 9, 2008 at 12:14 AM, Phillip G. <

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sam Rudd wrote:
| Before I start I’d like to say how happy I am for finding this forum,
| and the mailing list. I’m very glad to find like-minded Ruby enthusiasts
| like you guys!
|
| Right, as you can see from the link below, I have a custom-made IDE, but
| it’s got a blank box that I’d like to fill with a debugging tool, but I
| can’t find one. I’ve searched google, but still can’t find one that
| provides debugging and a runtime debug log. Does anyone know of/use such
| a tool, and can provide me a link?

While not technically a debugger, you could run autotest in that spot.
(ZenTest is the gem providing it, IIRC).

IME, tests and the Ruby stack trace (once you know where to look at),
together with liberally sprinkled puts statements is more useful than a
debugger.

YMMV, though.


Phillip G.
Twitter: twitter.com/cynicalryan

~ My behaviour is addictive functioning in a disease process of toxic
co-dependency. I need holistic healing and wellness before I’ll accept
any responsibility for my actions. – Calvin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkf7/HQACgkQbtAgaoJTgL9TgACfZjkPVFddZN0i/FeNw7n+o90f
4X0An2rD5xbyKNUQWTrqwv4mKp71Pdf5
=hiJA
-----END PGP SIGNATURE-----

I’m looking into ruby-debug, thanks. I’ll keep the debug window open,
but
once I get good enough at Ruby to make decent programs, I’ll test as I
go
using the built in tests.

Sorry if this posts twice, it keeps doing that for some reason.

Sam Rudd wrote:

| Before I start I’d like to say how happy I am for finding this forum,
While not technically a debugger, you could run autotest in that spot.
Twitter: twitter.com/cynicalryan
=hiJA
-----END PGP SIGNATURE-----

I think you really also ought to look hard at ruby-debug. It’s extremely
useful, in my estimation. Zentest isn’t quite the same approach to
coding errors, of course, but is still outstanding.

Finally, as a third, and possibly best approach of all, do check out
rspec.rubyforge.org.

I’m exploring all of these currently, and finding them all very much
worth my time.

Tom

Tom C., MS MA, LMHC
Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [email protected] >> (email)
<< TomCloyd.com >> (website & psychotherapy weblog)
<< sleightmind.wordpress.com >> (mental health issues weblog)
<< directpathdesign.com >> (web site design & consultation)

Phillip G. wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sam Rudd wrote:
| I’m looking into ruby-debug, thanks. I’ll keep the debug window open, but
| once I get good enough at Ruby to make decent programs, I’ll test as I go
| using the built in tests.

You should use TDD from the start. It is a good habit to get into, and
it helps thinking about what you want to do, too.

I used to work without tests, and quickly learned my lesson. Now, if I
change something in my code base, errors get caught before I embarrass
myself in public. :stuck_out_tongue:

I think that a debugger, for a languages like Ruby, is not really
useful. YMMV, though.


Phillip G.
Twitter: twitter.com/cynicalryan

~ I’m killing time while I wait for life to shower me with meaning and
happiness. – Calvin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkf+UEUACgkQbtAgaoJTgL+64wCbBmdUVM9xaVKzzchvvhkIGNhM
93UAn01wiVpy/1tziG0gQ0VuMePSZyCC
=aS+v
-----END PGP SIGNATURE-----

up

visit a rubyonrails website :http://www.rorchina.net
wolf union program club :http://wolf.rorchina.net
China Rubyonrails club: http://bbs.rorchina.net

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sam Rudd wrote:
| I’m looking into ruby-debug, thanks. I’ll keep the debug window open, but
| once I get good enough at Ruby to make decent programs, I’ll test as I go
| using the built in tests.

You should use TDD from the start. It is a good habit to get into, and
it helps thinking about what you want to do, too.

I used to work without tests, and quickly learned my lesson. Now, if I
change something in my code base, errors get caught before I embarrass
myself in public. :stuck_out_tongue:

I think that a debugger, for a languages like Ruby, is not really
useful. YMMV, though.


Phillip G.
Twitter: twitter.com/cynicalryan

~ I’m killing time while I wait for life to shower me with meaning and
happiness. – Calvin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkf+UEUACgkQbtAgaoJTgL+64wCbBmdUVM9xaVKzzchvvhkIGNhM
93UAn01wiVpy/1tziG0gQ0VuMePSZyCC
=aS+v
-----END PGP SIGNATURE-----

Phillip G. wrote:

You should use TDD from the start. It is a good habit to get into, and
Phillip G.
=aS+v
-----END PGP SIGNATURE-----

I appreciate your point of view, Phillip. I was excited to work with
ruby-debug, and I’m moving rapidly on to look at ZenTest and especially
at rspec. I’m predicting to myself that I’m going to end up with the
point of view you’ve just expressed. We’ll see.

t.

Tom C., MS MA, LMHC
Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [email protected] >> (email)
<< TomCloyd.com >> (website & psychotherapy weblog)
<< sleightmind.wordpress.com >> (mental health issues weblog)
<< directpathdesign.com >> (web site design & consultation)