• 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: What's most common cause of SIGSEGV and SIGBUS
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: What's most common cause of SIGSEGV and SIGBUS


  • Subject: Re: What's most common cause of SIGSEGV and SIGBUS
  • From: Ken Tozier <email@hidden>
  • Date: Sat, 13 Mar 2004 23:59:12 -0500

Thanks all.

Not releasing "kvParts" seems really leaky to me. Is this a real leak

No, it's not a leak. You didn't create kvParts with +alloc or -copy, and haven't sent it a -retain. Therefore you are not responsible for releasing it.



I don't know how Apple works these things behind the scenes, but coming from a C background, all this allocation going on inside a loop seems really wasteful. In C, you would just pass the address of a local struct and keep reusing the same block of memory. Ah well new tricks for old dogs...

Ken
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.


  • Prev by Date: Re: What's most common cause of SIGSEGV and SIGBUS
  • Next by Date: Re: Clicking Dock Icon creates a new window
  • Previous by thread: Re: What's most common cause of SIGSEGV and SIGBUS
  • Next by thread: Cocoa/Foundation and CoreFoundation
  • Index(es):
    • Date
    • Thread