• 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
Stopping in libMallocDebug messages
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Stopping in libMallocDebug messages


  • Subject: Stopping in libMallocDebug messages
  • From: Doug Hill <email@hidden>
  • Date: Tue, 2 Jan 2007 17:49:45 -0800

I'm trying to debug a memory corruption bug in my application. I link to libMallocDebug and set the appropriate environment variables to get the library to enable it's debugging features.
I'm now see a number of messages in the debugger console of this form:


libMallocDebug[MyApplication-5813]: target application recently wrote to freed malloc'd memory at: 0x12fc550, suggesting it didn't realize the memory had been freed
libMallocDebug[MyApplication-6879]: Attempting excessively large memory allocation: 251658239 bytes


The problem is I have no idea when these messages happen relative to what line code is executing at this point. It would be great to set breakpoints in the routine that prints the debug messages. Does anyone know what symbols I could set breakpoints on to get the debugger to stop when it prints one of these messages? I've looked through the libMallocDebug library for candidates and none seem to work. I've tried malloc_printf, a printf and a few others.

Any suggestions?

Doug Hill
Oracle Corp.
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


  • Follow-Ups:
    • Re: Stopping in libMallocDebug messages
      • From: Paul Walmsley <email@hidden>
References: 
 >ld -syslibroot reliability (From: Daniel Jalkut <email@hidden>)
 >Re: ld -syslibroot reliability (From: Eric Albert <email@hidden>)
 >Re: ld -syslibroot reliability (From: Daniel Jalkut <email@hidden>)

  • Prev by Date: Re: ld -syslibroot reliability
  • Next by Date: Re: Stopping in libMallocDebug messages
  • Previous by thread: Re: ld -syslibroot reliability
  • Next by thread: Re: Stopping in libMallocDebug messages
  • Index(es):
    • Date
    • Thread