I’m pleasant to announce the release of ruby-debug 0.1.3.
If you think that ruby-breakpoint is too limited for your needs and
debug.rb brings your application to its knees, you might find
this small extension useful.
INSTALL
It’s a usual procedure:
$ gem install ruby-debug
DOCS
This library has almost identical interface with the standard
debug.rblibrary.
I’m pleasant to announce the release of ruby-debug 0.1.3.
If you think that ruby-breakpoint is too limited for your needs and
debug.rb brings your application to its knees, you might find
this small extension useful.
Hello Kent,
This is great. Thanks for writing it.
One request I have, is that a carriage return with nothing on the line
run the
last next or step command. This is something I’m used to from the perl
debugger, which makes it nice to single step through your script.
Otherwise,
it’s a pain to have to type “n\n” or “s\n” to step through the script.
One request I have, is that a carriage return with nothing on the
line run the last next or step command. This is something I’m used
to from the perl debugger, which makes it nice to single step
through your script. Otherwise, it’s a pain to have to type “n\n”
or “s\n” to step through the script.
This flat-out rocks. I¹ve been happily developing sans debugger but the
print-statement route does presume you know the right things to print
out.
Reconstructing the steps to a given bug can be time consuming if you
have
the wrong set of print statements (read logger.debug calls) in place.
I¹ll
probably rely on the typical logger.debug and log tailing for most work,
but
this will certainly take the pain out of the hard-to-track bugs.
On Wednesday, July 12, 2006, at 12:15 PM, Kent S. wrote:
Hello Everyone,
I’m pleasant to announce the release of ruby-debug 0.1.3.
I’m unfortunately shackled on a Windows box for a good portion of my
time right now. Anyway to make this work on Windows? I get:
Building native extensions. This could take a while…
ERROR: While executing gem … (RuntimeError)
ERROR: Failed to build gem native extension.
Gem files will remain installed in c:/ruby/lib/ruby/gems/1.8/gems/
ruby-debug-0.1
.4 for inspection.
Results logged to c:/ruby/lib/ruby/gems/1.8/gems/ruby-debug-0.1.4/ext/
gem_make.o
ut
Unfortunately, I don’t have access to the Windows development
environment.
If somebody could make a precompiled gem, I would be more than happy to
make
it available for install.
I don’t see this warning. Are you using gcc 4.0.0? It seems that in
gcc 4.0.1 and higher this warning is suppressed by default. It is also
possible to suppress it with -fno-strict-aliasing. Anyway, I bet that
you should see this warning a couple of times when you compile ruby,
since I copied this particular usage from the ruby’s source code.
ruby_debug.c: Dans la fonction «create_binding» :
ruby_debug.c:640: attention : «context» may be used uninitialized in
gcc -shared -L"/usr/lib" -o ruby_debug.so ruby_debug.o -lruby1.8
zimbatm
In any cases this is not a problem for me. I just though you could
find this interesting
The only other gem compiled lib I use is mongrel and I don’t have that
output but I don’t know if it’s because it doesn’t use the same code
of if it was corrected.
–
Cheers,
zimbatm
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.