Pointers on debug'n, especially tracking an infinite loop.
Also is there a Ruby "binding" for ddd?
Thanx.
···
--
( o _ カラチ
// trans.
/ \ transami@runbox.com
I don't give a damn for a man that can only spell a word one way.
-Mark Twain
Pointers on debug'n, especially tracking an infinite loop.
Also is there a Ruby "binding" for ddd?
Thanx.
--
( o _ カラチ
// trans.
/ \ transami@runbox.com
I don't give a damn for a man that can only spell a word one way.
-Mark Twain
transami wrote:
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
transami wrote:
> 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
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.
> Also is there a Ruby "binding" for ddd?
I sincerely doubt it.
Too bad.
Thanks,
T.
On Tuesday 14 September 2004 12:48 am, Gavin Sinclair wrote:
--
( o _ カラチ
// trans.
/ \ transami@runbox.com
I don't give a damn for a man that can only spell a word one way.
-Mark Twain