Re: Guard Malloc Was Re: WWDC / XCode v2.0?
Re: Guard Malloc Was Re: WWDC / XCode v2.0?
- Subject: Re: Guard Malloc Was Re: WWDC / XCode v2.0?
- From: Tobias Sargeant <email@hidden>
- Date: Sun, 4 Jul 2004 15:48:33 +1000
On 04/07/2004, at 15:20, John Clements wrote:
That's a pretty impressive list in one tool, but I think XCode 1.5 /
2.0 has most of this list covered (please correct me if I'm wrong).
The Malloc Debug tool detects memory leaks. Guard Malloc handles most
of the rest (references to uninitialized memory, reading off the end
of an array, accesses to freed memory, etc.). Points I'm not sure
about are 4, 6 and 7 (don't even know what 7 is about :)
I believe I'm probably mostly responsible for this, and my reasons were
essentially that, in my opinion, the approaches taken by tools like
valgrind and purify represent a much more comprehensive, foolproof,
and, in some ways, more resource friendly approach to debugging memory
problems than do guard page approaches like Guard Malloc. If this
wasn't the case, the unix world would have stopped after the
development of Electric Fence and dbmalloc.
There's already a preliminary port of valgrind to PPC, and Apple is
already distributing GPLed build/debug tools (and thus has the
licensing issues sorted). This represents (again, IMO) a perfect
opportunity for Apple to give the OS X development world access to a
really first rate tool with a minimum of effort.
Toby.
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.