rocky / rbdbgr
- Source
- Commits
- Network (1)
- Issues (0)
- Downloads (0)
- Wiki (3)
- Graphs
-
Branch:
master
rocky (author)
Tue Feb 09 20:57:08 -0800 2010
rbdbgr /
| name | age | message | |
|---|---|---|---|
| |
.gitignore | Sun Sep 20 19:43:30 -0700 2009 | |
| |
ChangeLog | Sun Nov 01 18:04:47 -0800 2009 | |
| |
Makefile | Wed Aug 05 04:40:08 -0700 2009 | |
| |
README | Mon Nov 30 02:24:23 -0800 2009 | |
| |
Rakefile | Sun Dec 06 18:29:19 -0800 2009 | |
| |
app/ | Sun Jan 24 21:22:00 -0800 2010 | |
| |
bin/ | Mon Dec 07 03:07:14 -0800 2009 | |
| |
data/ | Thu Oct 22 05:01:06 -0700 2009 | |
| |
interface/ | Mon Nov 30 02:24:23 -0800 2009 | |
| |
io/ | Mon Nov 30 02:24:23 -0800 2009 | |
| |
lib/ | Mon Dec 07 03:07:14 -0800 2009 | |
| |
processor/ | Tue Feb 09 20:57:08 -0800 2010 | |
| |
profile/ | Sat Oct 31 18:38:00 -0700 2009 | |
| |
test/ | Tue Feb 09 13:51:26 -0800 2010 |
README
A modular, testable debugger for Ruby 1.9
Some cryptic examples.
Running if rbdbgr is installed:
rbdbgr ruby-program [program args]
To call from inside a Ruby program, there is one-time setup that
needs to be done first:
require 'rbdbgr'
mydbg = Debugger.new()
or if you haven't mucked around with $0 and ARGV, you might try:
mydbg = Debugger.new(:set_restart=>true))
which will tell the debugger how to "restart" the program.
If you want a synchronous stop in your program call to the
debugger at the point of the call, set opts[:immediate]
true. Example:
# ... work, work, work
mydbg.debugger(:immediate=>true) # enter debugger here
# ... work, work, work
However to enter the debugger on the next event after the
debugger() call:
# ... work, work, work
mydbg.debugger # Don't stop here...
work # but stop here.
And finally, if you want to debug just a block:
mydbg.debugger {
# ... code you want to debug.
}
