Re: tracking EXC_BAD_ACCESS error in applescript command
Re: tracking EXC_BAD_ACCESS error in applescript command
- Subject: Re: tracking EXC_BAD_ACCESS error in applescript command
- From: Jerry Krinock <email@hidden>
- Date: Sun, 20 Dec 2009 18:19:12 -0800
On 2009 Dec 20, at 13:50, François Guillet wrote:
> EXC_BAD_ACCESS error :
> #0 0x00007fff86951466 in -[NSScriptCommand _sendToRemainingReceivers] ()
> #1 0x00007fff86951fe5 in -[NSScriptCommand executeCommand] ()
> #2 0x00007fff8696902e in -[NSScriptingAppleEventHandler handleCommandEvent:withReplyEvent:] ()
> I implemented a subclass of NSScriptCommand used both for verb first or object first command : everything works fine, I can call [[self evaluatedReceivers] handleCommmand:self] from executeCommand without any problem. The EXC_BAD_ACCESS error, though, always happens if I try to call NSScriptCommand's executeCommand.
Not sure about the crash, but if you've subclassed NSScriptCommand, should not your subclass name appear in the call stack shown above, instead of NSScriptCommand? In your sdef, have you specified your subclass to be the Cocoa Class of this command?
_______________________________________________
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