Justin Clift <jclift(a)redhat.com> writes:
From watching the IRC conversation last few days, had a thought
that our (Aeolus's) poor debug-ability might be endemic to Ruby
in general. i.e. the platform itself, including many gems
If that's the case, are there good ruby debug tools and/or
good practises we should be following (enforcing) to make
things workable for ourselves and our end users?
As far as vanilla debugging goes, Greg put a nice thread out on the list
recently here:
https://fedorahosted.org/pipermail/aeolus-devel/2012-July/011352.html
I followed up with a note on ruby-debug being horribly broken on Ruby
1.9:
https://fedorahosted.org/pipermail/aeolus-devel/2012-July/011356.html
Since then I've learned that the 'debugger' gem is a fork of the old
'ruby-debug' gem. The former supports 1.9 just fine; the latter is
unmaintained. You can either grab the source
(
https://github.com/cldwalker/debugger), 'gem install debugger', or I've
also built RPMs for rubygem-debugger + deps here (F17):
http://jeckersb.fedorapeople.org/rubygem-debugger/
The 'debugger' gem works exactly the same as 'ruby-debug', so all of
Greg's instructions still apply.
Hope that helps!