Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Developer Center > Command line memory analyzer

Command line memory analyzer
Thread Tools
Senior User
Join Date: Feb 2003
Location: Atlanta
Status: Offline
Reply With Quote
Dec 6, 2003, 05:46 PM
 
Anyone know of any programs like Valgrind that are available for PPC?
2.16 Ghz Core 2 Macbook, 3GB Ram, 120 GB
     
Addicted to MacNN
Join Date: Mar 2000
Location: London, UK
Status: Offline
Reply With Quote
Dec 8, 2003, 11:55 AM
 
Perhaps if you explained what Valgrind actually is?
     
Mac Enthusiast
Join Date: Jul 2002
Status: Offline
Reply With Quote
Dec 8, 2003, 08:45 PM
 
Angus_D: Cmd-L, tab, Valgrind, enter.

Coolmacdude: If you are talking about OS X, and not just PPC, then:

For malloc error catching, man malloc. There are several env variables you can set to catch writes to dealloc'ed chunks and stack logging for leaks etc.

Also see MallocDebug and (for ObjC) ObjectAlloc which give you nice allocation tree tables etc.

For profiling, look at CHUD, especially Shark.
     
Professional Poster
Join Date: Apr 2001
Location: Long Beach, CA
Status: Offline
Reply With Quote
Dec 8, 2003, 10:01 PM
 
Originally posted by arekkusu:
Angus_D: Cmd-L, tab, Valgrind, enter.
You are assuming that the OS X Unix kernel guru is using Safari. Now what would make you assume that? Hmmm???

ACSA 10.4/10.3, ACTC 10.3, ACHDS 10.3
     
Mac Enthusiast
Join Date: Jul 2002
Status: Offline
Reply With Quote
Dec 9, 2003, 10:23 AM
 
Originally posted by Detrius:
You are assuming that the OS X Unix kernel guru is using Safari. Now what would make you assume that? Hmmm???
Regardless of what browser you use, it takes less time to google a word than it does to post here.
     
Senior User
Join Date: Feb 2003
Location: Atlanta
Status: Offline
Reply With Quote
Dec 9, 2003, 07:34 PM
 
Originally posted by arekkusu:

For malloc error catching, man malloc. There are several env variables you can set to catch writes to dealloc'ed chunks and stack logging for leaks etc.
I checked that out but I still like Valgrind a lot better since it gives you a printout of all the errors at once when the program exits instead of core dumping on the first one like most of the other checkers do.
2.16 Ghz Core 2 Macbook, 3GB Ram, 120 GB
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 02:30 PM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2