On 10/12/06, Hugh Sasse <hgs / dmu.ac.uk> wrote:
> I have a large application (which is actually a Rails app) which is
> behaving oddly (I can change items in a DB twice, but 4 times
> fails), and using all the conventional approaches I have learned for
> debugging (printing things out, logging to files, ...) it is taking
> me an age to track the problem down.  I have no good reason to assert
> that the database or Rails is at fault, it is more likely to be my
> code, but the interactions with the other code make debugging more
> difficult.

My first bet would be on improving the test case suite. But in the
process I think that a good debugger is a very valuable tool too. You
can try ruby-debug, which I find very helpful sometimes:

http://datanoise.com/articles/2006/09/14/debugging-rails-application

-- 
Kent
---
http://www.datanoise.com