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: John Clements <email@hidden>
- Date: Sat, 3 Jul 2004 22:20:10 -0700
This thread has diverged, somewhat bizarrely, into a discussion of Unix
debugging tools. This is an attempt to connect it back to XCode.
First, here is what the Valgrind user manual says it is good for..
Valgrind can detect problems such as:
1 Use of uninitialised memory
2 Reading/writing memory after it has been free'd
3 Reading/writing off the end of malloc'd blocks
4 Reading/writing inappropriate areas on the stack
5 Memory leaks -- where pointers to malloc'd blocks are lost forever
6 Mismatched use of malloc/new/new [] vs free/delete/delete []
7 Some misuses of the POSIX pthreads API
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 :)
The ease of use with Guard Malloc in new version of XCode (simply
toggle a menu item) is awsome. The price is very slow execution (two
orders of magnitude). As Eric Albert suggests, filing a bug report
would be a good idea - especially in the next week or so. The Apple
developer tools team will return from WWDC with a long list of exciting
new ideas. Bring them back down to earth. Suggest they apply Shark to
Guard Malloc !!
John.
_______________________________________________
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.