On Nov 5, 1:09 am, Santosh Turamari <[EMAIL PROTECTED]> wrote: > Hi, > I am facing the difficulty in understanding the output of valgrind > memory leaks. How to interpret it. pls help me out.
For the ruby interpreter, you should probably think about running valgrind with the following options: --partial-loads-ok=yes --undef-value-errors=no However, you probably shouldn't be using valgrind to try to debug memory leaks in Ruby or Rails -- valgrind is going to see memory malloc()ed by the Ruby interpreter for fast object allocation as a leak, which it isn't. Plus, valgrind is going to tell you where in the C code (ruby interpreter source code) the leak "appears" to come from -- which is totally useless for what you're probably trying to do. I recommend using Bleak House instead to track down Ruby and Rails memory leaks: http://blog.evanweaver.com/files/doc/fauna/bleak_house/files/README.html Good luck. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
