Re: ProjectCenter segfault

[Serg Stoyan]

Hi Stefan,

> On 2003-07-11 01:50:49 +0200 Alexander Malmberg <alexander@malmberg.org>
> wrote:
[snip]
> > It's also pickier now than before. Forwarding won't work at all
unless
> > you implement -methodSignatureForSelector:.
> > 
> 
> Sure you have to. Even in apple docs you have higlighted text in a box
> saying:
> 
> Note: To respond to methods that your object does not itself recognize,
> you must override methodSignatureForSelector: in addition to
> forwardInvocation:. The mechanism for forwarding messages uses
> information obtained from methodSignatureForSelector: to create the
> NSInvocation object to be forwarded. Your overriding method must provide
> an appropriate method signature for the given selector, either by
> preformulating one or by asking another object for one.
> 
> And it is logical. I think that the latest change, and usage of selector
> from object to which invocation is being sent, revealed other bugs in GS
> (think of it as Good).

Ok, after implementing this inside PCAppControlller.m

- (NSMethodSignature *)methodSignatureForSelector:(SEL)aSelector
{
  if ([menuController respondsToSelector: aSelector])
    {
      return [menuController methodSignatureForSelector:aSelector];
    }

  return nil;
}

we get:

vacall: va_start type 14 and va_return type 0 disagree.
Aborted

I've repotred this bug about Preferences application which seems to use
methodSignatureForSelector: method also. Maybe there is some problems with
ffcall library?

-- 
Serg Stoyan