• 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: AULab calling unimplemented -saveDataInDictionary:forDocument in my CocoaView???
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AULab calling unimplemented -saveDataInDictionary:forDocument in my CocoaView???


  • Subject: Re: AULab calling unimplemented -saveDataInDictionary:forDocument in my CocoaView???
  • From: "tahome izwah" <email@hidden>
  • Date: Tue, 16 Sep 2008 22:22:32 +0200

Thanks for the suggestion. That's what I did, but the problem appears
to be somewhere else because when the exception gets raised I get the
following stack trace:

#0	0x002fbab8 in -[NSException raise]
#1	0x00cdf614 in -[NSCarbonMenuImpl
performActionWithHighlightingForItemAtIndex:]
#2	0x00cc0d90 in AppKitMenuEventHandler
#3	0x01d9b3cc in DispatchEventToHandlers
#4	0x01d9a564 in SendEventToEventTargetInternal
#5	0x01db7464 in SendEventToEventTarget
#6	0x01decf00 in SendHICommandEvent
#7	0x01e1384c in SendMenuItemSelectedEvent
#8	0x01e13750 in FinishMenuSelection
#9	0x01df0414 in MenuSelectCore
#10	0x01defe28 in _HandleMenuSelection2
#11	0x00c129e0 in _NSHandleCarbonMenuEvent
#12	0x00b88540 in _DPSNextEvent
#13	0x00b87a14 in -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:]
#14	0x00b816d0 in -[NSApplication run]
#15	0x00b520d4 in NSApplicationMain

...which is not very helpful, and I have no clue how to debug a
problem like this ... :-(

Thanks again
--th

2008/9/16 Brian Willoughby <email@hidden>:
> You might have two objects cross-linked somehow.  For example, a pointer to
> an object could be reallocated without you knowing it, maybe because of a
> stack error in your code, or reference counting problems in your code.
>  There's actually a surprising number of potential reasons why you might end
> up with a bad method selector.
>
> I suggest that you run your AU in the Xcode debugger, and specify AULab as
> the executable.  Then you can back trace through the call stack and see the
> origin of this mess.  It should be clear at that point whether it's your
> error, or stack/memory problems, or something else.
>
> Brian Willoughby
> Sound Consulting
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: AULab calling unimplemented -saveDataInDictionary:forDocument in my CocoaView???
      • From: Brian Willoughby <email@hidden>
References: 
 >AULab calling unimplemented -saveDataInDictionary:forDocument in my CocoaView??? (From: "tahome izwah" <email@hidden>)
 >Re: AULab calling unimplemented -saveDataInDictionary:forDocument in my CocoaView??? (From: Brian Willoughby <email@hidden>)

  • Prev by Date: Re: Dithering??
  • Next by Date: Re: Dithering??
  • Previous by thread: Re: AULab calling unimplemented -saveDataInDictionary:forDocument in my CocoaView???
  • Next by thread: Re: AULab calling unimplemented -saveDataInDictionary:forDocument in my CocoaView???
  • Index(es):
    • Date
    • Thread