[ANN] ruby-debug 0.1.3

Hello Everyone,

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.

Also you can check out my little tutorial at
http://www.datanoise.com/articles/2006/07/12/tutorial-on-ruby-debug

Cheers,
Kent.

Kent S. wrote:

Hello Everyone,

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.

Regards,
Blair


Blair Z., Ph.D.
[email protected]
Subversion training, consulting and support
http://www.orcaware.com/svn/

On Jul 12, 2006, at 4:51 PM, Blair Z. wrote:

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.

Regards,
Blair

+1

-Ezra

fr kent:

Also you can check out my little tutorial at

http://www.datanoise.com/articles/2006/07/12/tutorial-on-ruby-debug

very cool. is this pure ruby?
kind regards -botp

Blair,

You are right, for some reason it slipped from the original
implementation. I’ve added it back.

Thank you.

On 7/12/06, Blair Z. [email protected] wrote:


Blair Z., Ph.D.
[email protected]
Subversion training, consulting and support
http://www.orcaware.com/svn/


Kent

http://www.datanoise.com

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.

Thanks for this.

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

D:\RailsWorkspace\equipment_now>

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.

On 13 Jul 2006 03:03:52 -0000, BA Baracus
[email protected]

Peña,
No, it’s not. There is an almost identical library bundled with Ruby
called debug.rb which is pure ruby. It’s just much slower.

Kent.

This lib looks nice. For info :

sudo gem install ruby-debug
Password:
Attempting local installation of ‘ruby-debug’
Local gem file not found: ruby-debug*.gem
Attempting remote installation of ‘ruby-debug’
Building native extensions. This could take a while…
ruby_debug.c: Dans la fonction «check_breakpoints» :
ruby_debug.c:198: attention : parenthèses suggérées autour de && Ã
l’intérieur de ||
ruby_debug.c: Dans la fonction «create_binding» :
ruby_debug.c:218: attention : déréférencement du pointeur type-punned
brisera les strictes d’aliases
ruby_debug.c: Dans la fonction «debug_event_hook» :
ruby_debug.c:396: attention : unused variable «found»
ruby_debug.c:274: attention : unused variable «debug_breakpoint»
ruby_debug.c: Dans la fonction «debug_interrupt_last» :
ruby_debug.c:576: attention : unused variable «thread»
ruby_debug.c: Dans la fonction «debug_check_started» :
ruby_debug.c:72: attention : control reaches end of non-void function
ruby_debug.c: Dans la fonction «debug_suspend» :
ruby_debug.c:640: attention : «context» may be used uninitialized in
this function
ruby_debug.c: Dans la fonction «debug_resume» :
ruby_debug.c:672: attention : «context» may be used uninitialized in
this function
ruby extconf.rb install ruby-debug
creating Makefile

make
gcc -fPIC -Wall -g -O2 -fPIC -I. -I/usr/lib/ruby/1.8/i486-linux
-I/usr/lib/ruby/1.8/i486-linux -I. -c ruby_debug.c
gcc -shared -L"/usr/lib" -o ruby_debug.so ruby_debug.o -lruby1.8
-lpthread -ldl -lcrypt -lm -lc

make install
/usr/bin/install -c -m 0755 ruby_debug.so
/usr/lib/ruby/gems/1.8/gems/ruby-debug-0.1.4/lib
Successfully installed ruby-debug-0.1.4


Cheers,
zimbatm

http://zimbatm.oree.ch

Hi Kent, there is still one warning in 0.1.5 in case you want to see :

Attempting remote upgrade of ruby-debug
Attempting remote installation of ‘ruby-debug’
Building native extensions. This could take a while…
ruby_debug.c: Dans la fonction «create_binding» :
ruby_debug.c:227: attention : déréférencement du pointeur type-punned
brisera les strictes d’aliases
ruby extconf.rb update
creating Makefile

make
gcc -fPIC -Wall -g -O2 -fPIC -I. -I/usr/lib/ruby/1.8/i486-linux
-I/usr/lib/ruby/1.8/i486-linux -I. -c ruby_debug.c
gcc -shared -L"/usr/lib" -o ruby_debug.so ruby_debug.o -lruby1.8
-lpthread -ldl -lcrypt -lm -lc

make install
/usr/bin/install -c -m 0755 ruby_debug.so
/usr/lib/ruby/gems/1.8/gems/ruby-debug-0.1.5/lib
Successfully installed ruby-debug-0.1.5


Cheers,
zimbatm

http://zimbatm.oree.ch

Jonas,

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.

On 7/14/06, Jonas P. [email protected] wrote:

http://lists.rubyonrails.org/mailman/listinfo/rails


Kent

http://www.datanoise.com

Thanks. I’ve removed these warnings in the latest version. For some
reason my ruby was compiled without -Wall.

On 7/13/06, Jonas P. [email protected] wrote:

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

http://zimbatm.oree.ch


Rails mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails


Kent

http://www.datanoise.com

Hi Kent,

I use gcc 4.0.3 (Ubuntu 4.0.3-1ubuntu5)

In any cases this is not a problem for me. I just though you could
find this interesting :slight_smile:

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

http://zimbatm.oree.ch

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs