Re: -[NSInvocation length]: selector not recognized [self = 0x30abd0]
Re: -[NSInvocation length]: selector not recognized [self = 0x30abd0]
- Subject: Re: -[NSInvocation length]: selector not recognized [self = 0x30abd0]
- From: "Clark Cox" <email@hidden>
- Date: Sun, 23 Sep 2007 14:26:15 -0700
On 9/23/07, NSTask <email@hidden> wrote:
> Hi Jim,
>
>
> On 9/23/07, Jim Correia <email@hidden> wrote:
> >
> > On Sep 23, 2007, at 3:33 PM, NSTask wrote:
> >
> > > I am posting this question again today, hoping somebody can give me
> > > a clue what I am missing. I am using distributed objects and
> > > managed to talk to server. Client is getting responses successfully
> > > from the server. However the problem is when client receives
> > > session id from the server and try to use that session id for
> > > further queries with the soap api it always get the error message
> > > from the server saying
> > >
> > > -[NSInvocation length]: selector not recognized [self = 0x30abd0]
> >
> > If this error isn't the result of you obviously sending an message to
> > an object which doesn't understand it, it is often the result of
> > sending a message to a deallocated object (and a new object happens
> > to exist at the same address as the old object.)
> >
> > NSZombie (in addition to reviewing your memory management code) is
> > your first step to debugging this problem.
>
>
>
> NSZombie has returned this.
>
> Selector 'retain' sent to dealloced instance 0x30ca40 of class NSInvocation.
> Break at '-[_NSZombie retain]' to debug.
Have you followed the advice given in that message? If you do so, then
you'll see who exactly is retaining the dead object.
--
Clark S. Cox III
email@hidden
_______________________________________________
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