I use my own little IDE that I developed so I can write Pascal with
Cocoa and wanted to make a light-weight GUI for the leaks utility that
I could use from my app is the reason for doing this. Otherwise yes,
using MallocDebug is better. It's really fast and handy to call leaks
instead of loading MallocDebug.
On Jun 13, 2009, at 12:04 PM, Chris Suter wrote:
Hi Ryan,
On Fri, Jun 12, 2009 at 9:29 PM, Ryan Joseph<thealchemistgu...@gmail.com
> wrote:
I wasn't sure where to post this but Cocoa programmers should know
as well
as any one else I thought.
I have just learned about the "leaks" unix utility for detecting
memory
leaks but I'm not unix savvy enough to understand a point mentioned
in the
man page. Which is:
"If the MallocStackLogging environment variable was set when the
application
was launched, leaks also displays a stack trace describing where
the buffer
was allocated."
Can anyone who uses this utility tell me how to set the this
environment
variable? I'm thinking it's possible this must be set via GDB,
otherwise I'm
not sure where it could get a stack trace from. Thank you for
helping.
It's easier if you use MallocDebug or Instruments.
Regards,
Chris
Regards,
Josef
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
