rbtrace 0.2.2 → 0.2.3
Sign up to get free protection for your applications and to get access to all the features.
- data/bin/rbtrace +4 -2
- data/rbtrace.gemspec +1 -1
- metadata +3 -3
data/bin/rbtrace
CHANGED
@@ -75,7 +75,7 @@ class RBTracer
|
|
75
75
|
# Returns nothing.
|
76
76
|
def self.cleanup_queues
|
77
77
|
if (pids = `ps ax -o pid`.split("\n").map{ |p| p.strip.to_i }).any?
|
78
|
-
ipcs = `ipcs -q`.split("\n").grep(/^q/).map{ |line| line
|
78
|
+
ipcs = `ipcs -q`.split("\n").grep(/^(q|0x)/).map{ |line| line[/(0x[a-f0-9]+)/,1] }
|
79
79
|
ipcs.each do |ipci|
|
80
80
|
next if ipci.match(/^0xf/)
|
81
81
|
|
@@ -364,7 +364,7 @@ class RBTracer
|
|
364
364
|
opts = Trollop.options do
|
365
365
|
version <<-EOS
|
366
366
|
rbtrace: like strace, but for ruby code
|
367
|
-
version 0.2.
|
367
|
+
version 0.2.3
|
368
368
|
(c) 2011 Aman Gupta (tmm1)
|
369
369
|
http://github.com/tmm1/rbtrace
|
370
370
|
EOS
|
@@ -374,6 +374,8 @@ rbtrace shows you method calls happening inside another ruby process in real tim
|
|
374
374
|
|
375
375
|
to use rbtrace, simply `require "rbtrace"` in your ruby app.
|
376
376
|
|
377
|
+
for examples and more information, see http://github.com/tmm1/rbtrace
|
378
|
+
|
377
379
|
Usage:
|
378
380
|
|
379
381
|
rbtrace -p <PID> # trace the given process
|
data/rbtrace.gemspec
CHANGED
metadata
CHANGED