# Documented practical debugger workflow / tools?

**URL:** <https://www.ruby-forum.com/t/documented-practical-debugger-workflow-tools/89950>\
**Category:** Ruby\
**Created:** [March 24, 2007, 4:55am UTC](https://www.ruby-forum.com/t/documented-practical-debugger-workflow-tools/89950 "2007-03-24T04:55:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Demetrius\_G](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/ebca7d/32.png) [@Demetrius\_G](https://www.ruby-forum.com/u/Demetrius_G)\
**Post date:** [March 24, 2007, 4:55am UTC](https://www.ruby-forum.com/t/documented-practical-debugger-workflow-tools/89950/1 "2007-03-24T04:55:18Z")

</div>

I am looking for practical examples of effective debugging workflow in  
ruby that is documented.

Currently, I see ruby documentation explain installation and running  
ruby, starting with the most ancient standard input and ^D. But I  
don’t see any real workflow examples of using whatever tools exist  
there. I’ve read about debugging via text commands, but is this what  
everyone is using and expected?

A documented debugging workflow can allow others to review and even  
see if improvements can be made, but right now I can find extremely  
little on the tools and interfaces used for effective  
(time/usefulness) debugging in a ruby environment.