debig an infinite loop

[trans. (T. Onoma)]

Pointers on debug'n, especially tracking an infinite loop.

Also is there a Ruby "binding" for ddd?

Thanx.

--
( o _ カラãƒ
// trans.
/ \ (e-mail address removed)

I don't give a damn for a man that can only spell a word one way.
-Mark Twain

 

[Gavin Sinclair]

Pointers on debug'n, especially tracking an infinite loop.

My preferred method of debugging is to open an irb shell from the program.
This lets you evaluate local variables, etc. See Florian Weber's recent
"breakpoint.rb" announcement.

loop do
...
breakpoint if some_condition
...
end

For an infinite loop, I'm guessing printf-debugging would help as well.
Thus: puts/logger/log4r.

Also is there a Ruby "binding" for ddd?

I sincerely doubt it.

Cheers,
Gavin

 

[Florian Gross]

My preferred method of debugging is to open an irb shell from the program.
This lets you evaluate local variables, etc. See Florian Weber's recent
"breakpoint.rb" announcement.

Nice to see this getting adopted so quickly.

Note that in this context even an assert() might be useful. (Something
like assert { termination condition })

Cheers,
Gavin

Regards,
Florian %w{Gross Weber}.any #

 

[trans. (T. Onoma)]

My preferred method of debugging is to open an irb shell from the program.
This lets you evaluate local variables, etc. See Florian Weber's recent
"breakpoint.rb" announcement.

loop do
...
breakpoint if some_condition
...
end

Yes, that seems pretty nice. I plan to use that.

For an infinite loop, I'm guessing printf-debugging would help as well.
Thus: puts/logger/log4r.

Although I did figure it out already, it was tricky b/c the loop was occurring
in someone else's library.

I sincerely doubt it.

Too bad.

Thanks,
T.

--
( o _ カラãƒ
// trans.
/ \ (e-mail address removed)

I don't give a damn for a man that can only spell a word one way.
-Mark Twain