• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Memory Leak
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Memory Leak


  • Subject: Re: Memory Leak
  • From: "Sean McBride" <email@hidden>
  • Date: Mon, 26 May 2008 15:32:14 -0400
  • Organization: Rogue Research

On 5/26/08 11:25 AM, Greg Guerin said:

>Sean McBride wrote:
>
>>Finding leaks with Instrument/MallocDebug/leaks requires
>>breaking one's workflow.  If Xcode printed leaks after every run, it
>>would be easier to find leaks _right away_ instead of weeks later when
>>one decides to run it through a special tool.
>
>man atexit
>
>Set bkpt on your function.

OK, so one installs an atexit() handler, then what?  Use system() to
invoke the 'leaks' command line tool?  I suppose that could work.  But
it's a lot of hocus pocus for someone new to the platform.

My point was only that competing IDEs (ie Visual Studio) essentially do
this magic for you, and that I think it would be a great feature for
Xcode to have.

--
____________________________________________________________
Sean McBride, B. Eng                 email@hidden
Rogue Research                        www.rogue-research.com
Mac Software Developer              Montréal, Québec, Canada

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: Memory Leak (From: Greg Guerin <email@hidden>)

  • Prev by Date: XCode 3 and Intel Compilers
  • Next by Date: Re: Memory Leak
  • Previous by thread: Re: Memory Leak
  • Next by thread: Re: Memory Leak
  • Index(es):
    • Date
    • Thread