unroller 0.0.22 → 0.0.23
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/Readme +20 -3
- metadata +1 -1
data/Readme
CHANGED
|
@@ -64,15 +64,32 @@ Screenshot[link:include/screenshot_interactive.png]
|
|
|
64
64
|
|
|
65
65
|
(The above shows <tt>:display_style => :show_entire_method_body</tt>.)
|
|
66
66
|
|
|
67
|
+
===Interactive debugger
|
|
68
|
+
|
|
69
|
+
Currently there are two basic modes: non-interactive trace mode and interactive debugger mode. To enable the latter, just call <tt>Unroller::debug</tt>, kind of like this:
|
|
70
|
+
|
|
71
|
+
Unroller::debug do
|
|
72
|
+
whatever()
|
|
73
|
+
end
|
|
74
|
+
|
|
75
|
+
It will prompt you after every line of code and ask you what to do. Currently the options are:
|
|
76
|
+
* <b>step out</b>
|
|
77
|
+
* <b>step over</b>
|
|
78
|
+
* <b>step into</b>
|
|
79
|
+
* <b>show locals</b>: lists all local variables and their variables (using pp pretty printer)
|
|
80
|
+
* <b>run</b>: ends interactive mode
|
|
81
|
+
|
|
82
|
+
<b>The interactive debugger is still pretty experimental and is sure to still have some bugs in it!</b>
|
|
83
|
+
|
|
67
84
|
===Inspecting variables
|
|
68
85
|
|
|
69
86
|
If you'd like to see the values of all arguments/parameters that were passed into the method for each method call, just pass in the <tt>:show_args => true</tt> option.
|
|
70
87
|
|
|
71
88
|
If you'd like to see the values of all local variables as they exist right before executing the current line, just pass in the <tt>:show_locals => true</tt> option.
|
|
72
89
|
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
Also, I haven't yet figured out a way to show the return value it's going to return with when we hit a 'return' event. That would be nice to have, too, if one can figure out how to implement it...
|
|
90
|
+
Not implemented:
|
|
91
|
+
* You might like to know that the state of those variables is _after_ executing that line, too, but currently that's not implemented. (Use the interactive debugger instead.)
|
|
92
|
+
* Also, I haven't yet figured out a way to show the return value it's going to return with when we hit a 'return' event. That would be nice to have, too, if one can figure out how to implement it...
|
|
76
93
|
|
|
77
94
|
===Only tracing if a condition is met
|
|
78
95
|
|
metadata
CHANGED
|
@@ -3,7 +3,7 @@ rubygems_version: 0.9.2
|
|
|
3
3
|
specification_version: 1
|
|
4
4
|
name: unroller
|
|
5
5
|
version: !ruby/object:Gem::Version
|
|
6
|
-
version: 0.0.
|
|
6
|
+
version: 0.0.23
|
|
7
7
|
date: 2007-06-18 00:00:00 -07:00
|
|
8
8
|
summary: "Ruby Code Unroller: A tool for generating human-readable \"execution traces\""
|
|
9
9
|
require_paths:
|