• 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: leak detecting vs memory
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: leak detecting vs memory


  • Subject: Re: leak detecting vs memory
  • From: Dave MacLachlan <email@hidden>
  • Date: Thu, 01 Dec 2005 12:51:48 -0800

Are you sure that you didn't just fill all 4G of VM space?

Cheers,
Dave

On Dec 1, 2005, at 12:32 PM, David Dunham wrote:

I routinely like to leave MallocStackLogging set (in the info dialog for my executable), so I can perform leak detection whenever I feel like it. However, I went out to lunch, and got

Acropolis-D(419,0xa000ed68) malloc: *** out of memory while stack logging
Program received signal: "SIGABRT".


Is there a way to change the size of this stack?
--

David Dunham A Sharp, LLC
Voice/Fax: 206 783 7404 http://a-sharp.com
Efficiency is intelligent laziness.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40adobe.com


This email sent to email@hidden

_______________________________________________ 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: 
 >leak detecting vs memory (From: David Dunham <email@hidden>)

  • Prev by Date: leak detecting vs memory
  • Next by Date: Re: Safari Plug-in and Universal Binary
  • Previous by thread: leak detecting vs memory
  • Next by thread: Re: leak detecting vs memory
  • Index(es):
    • Date
    • Thread