• 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: Crash at THFSPlusStore::LessThan(HFSUniStr255 const&)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Crash at THFSPlusStore::LessThan(HFSUniStr255 const&)


  • Subject: Re: Crash at THFSPlusStore::LessThan(HFSUniStr255 const&)
  • From: Jens Alfke <email@hidden>
  • Date: Tue, 12 Feb 2008 15:49:31 -0800

These kinds of memory smashers can be hard to track down. I would start by setting the environment variable MallocScribble to 1. This will overwrite freed blocks with a repeating 0x55 pattern, which will help flush out places where something is reading from a freed block. (It's cheap enough that I always set it up in my executable settings in Xcode, and in my .gdbinit.)

The heavy-duty tool for detecting smashers is libgmalloc. I've actually never used it, but I believe there is documentation in the system. It vastly increases memory usage and slows your code to a crawl, though, so it might take hours to get to the point of the crash...

—Jens_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


References: 
 >Crash at THFSPlusStore::LessThan(HFSUniStr255 const&) (From: Daniel Cote <email@hidden>)

  • Prev by Date: Listen for Words in the Language Model
  • Next by Date: Re: Repetitive Appending of Strings
  • Previous by thread: Crash at THFSPlusStore::LessThan(HFSUniStr255 const&)
  • Next by thread: NSString ASCII filter
  • Index(es):
    • Date
    • Thread