On 27/07/2012, at 10:32 AM, John Eckersberg wrote:
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?
<snip>
The 'debugger' gem works exactly the same as
'ruby-debug', so all of
Greg's instructions still apply.
Ahhh, bad wording on my part. Not sure what wording to use
instead, so I'll describe it... :)
By "poor debug-ability", I mean for (SysAdmin) end users, so
they can tell what's going on in our software when a problem
occurs.
With many software packages, that's what the log files do.
For us though, our log files aren't effective for that.
It also _seems_ (my impression) that they're not super
effective even for developers's who hit problems outside of
what they're working on already very familiar with.
Suspecting it's not just an Aeolus problem here, but fairly
common among Ruby community. (this last bit is just an
impression)
For Aeolus (ie Conductor), have I just forgotten something
simple, like being able to increase log verbosity settings
or something?
Regards and best wishes,
Justin Clift
--
Aeolus Community Manager
http://www.aeolusproject.org