• 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: file scan results in EX_BAD_ACCESS
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: file scan results in EX_BAD_ACCESS


  • Subject: Re: file scan results in EX_BAD_ACCESS
  • From: Daniel Child <email@hidden>
  • Date: Sat, 01 Sep 2007 11:18:02 -0400

The culprit was the dealloc method call if (self) [release self] prior to calling [super dealloc].

I don't understand why that would be a problem. Is the reference to super lost if yo release self?

On Sep 1, 2007, at 12:11 AM, Shawn Erickson wrote:

On 8/31/07, Daniel Child <email@hidden> wrote:

The only code that gets called is what you saw

...except for -[DataParser init], -[DataParser dealloc], etc. :)

-Shawn

_______________________________________________

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


  • Follow-Ups:
    • Re: file scan results in EX_BAD_ACCESS
      • From: Chris Williams <email@hidden>
  • Prev by Date: Re: file scan results in EX_BAD_ACCESS
  • Next by Date: Re: NSBezierPath append CGGlyph
  • Previous by thread: Re: initializing ivars
  • Next by thread: Re: file scan results in EX_BAD_ACCESS
  • Index(es):
    • Date
    • Thread