Fwd: -[NSInvocation length]: selector not recognized [self = 0x30abd0]
Fwd: -[NSInvocation length]: selector not recognized [self = 0x30abd0]
- Subject: Fwd: -[NSInvocation length]: selector not recognized [self = 0x30abd0]
- From: NSTask <email@hidden>
- Date: Sun, 23 Sep 2007 23:27:10 +0200
On 9/23/07, Jim Correia <email@hidden> wrote:
>
> On Sep 23, 2007, at 4:14 PM, NSTask wrote:
>
> > NSZombie has returned this.
> >
> > Selector 'retain' sent to dealloced instance 0x30ca40 of class
> > NSInvocation.
> > Break at '-[_NSZombie retain]' to debug.
>
> So an instande of NSInvocation is being used, but has been deallocated.
>
> Are you using NSInvocation directly?
Yes, I am using NSInvocation directly.
Follow the advice of the logged message, and when you stop look at
> the backtrace and work backwards to find the memory management bug.
I backtraced it to see the memory management bug and fixed it. By the time
object
reaches to the client it automatically gets released.
So for testing I retained it again and got this
[NSConcreteData _fastCharacterContents]: selector not recognized [self =
0x30d000]
/S.
_______________________________________________
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