Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

DanKegel

macrumors newbie
Original poster
May 28, 2009
1
0
http://blog.mozilla.com/nnethercote/2009/05/28/mac-os-x-now-supported-on-the-valgrind-trunk/

Looks like Valgrind 3.5.0 will support the Mac!

You can use it already by checking it out from the svn trunk and
building it yourself. We use it in the Chromium continuous build and test
system, and it has caught quite a few issues (some in Mac OS X itself,
including a rather heinous ATI driver problem that crashes Display Manager).

http://groups.google.com/group/vim_mac/msg/2bfd871b82c9b3b1
is an example of someone using it to find a bug in Mac Vim.
(Though that was written before the merge to trunk, so it still
refers to the old DARWIN branch.)

Also note: if you want line numbers, you need to generate a dSYM file, which can be slow.
 
This is very big news. I've been waiting for this for probably 4 years or more now, and I'm sure others have been waiting even longer. Thanks for passing along the great news!
 
I know this is an old thread but I just checked out the Valgrind SVN release and it seems to work well although I am still a little confused as to why Valgrind is better than using Instruments and Shark though?

Can anyone shed some light on that for me?
 
Shark is almost exclusively a performance tool. Instruments is a sort of performance/behavioral insight hybrid tool. Valgrind is very much a correctness tool, although a few performance tools (Cachegrind, etc...) run on its foundation.
 
So, the set of tools that an Objective-C programmer would be well advised to include in their arsenal for debugging and checking correctness is at least:
  • Instruments
  • Guard Malloc
  • Valgrind
  • Clang (eg, through AnalysisTool)
Any other useful tips?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.