Re: Debugging cocoa
Re: Debugging cocoa
- Subject: Re: Debugging cocoa
- From: tahome izwah <email@hidden>
- Date: Sat, 21 Feb 2009 14:27:56 +0100
Looks like you're right. I just tried this myself with a new project
and it doesn't jump into the debugger, but I never had this problem
before so it must have been introduced recently...
I recommend you file a bug about this at http://bugreporter.apple.com
HTH
--th
2009/2/21 john smith <email@hidden>:
>
>
> Please, could it really be that noone has had this problem?
>
> I create the au + cocoaview template. I don't "mess" with the project. I set
> breakpoints: The c++ breakpoints are triggered, the obj-c breakpoints are
> not.
>
> Clearly the debugger has not realised that the cocoa code has been loaded
> (this I can see on the breakpoint colour)
>
> I tried using AULab and CocoaAUHost.
>
>
> Thanks,
>
> Michael Olsen
>
>
>> Date: Fri, 20 Feb 2009 08:36:53 -0300
>> Subject: Re: Debugging cocoa
>> From: email@hidden
>> To: email@hidden
>> CC: email@hidden
>>
>> I discovered that a good way of debugging an AU is to modify the
>> sample CocoaAUHost (I'm not sure if this is the right name; I'm not on
>> my Mac right now; anyway ,look at the CoreAudio examples folder) to
>> host just your particular AU. Then, when you run the host in the
>> debugging mode, log messages of your AU are displayed at the console.
>> Marcelo Cicconet.
>>
>> On Fri, Feb 20, 2009 at 7:34 AM, john smith <email@hidden> wrote:
>> >
>> >
>> > Hi,
>> > I build an AU with a cocoa view using the XCode template. I'm trying to
>> > debug it, using AULab, but unfortunately breakpoints are only triggered
>> > in
>> > the carbon (i.e. the "effect") part of the code.
>> > In the cocoa code the breakpoints have the colour that indicates that
>> > the
>> > code is not loaded.
>> > My best guess is that it seems there's 2 copies of the bundle.. One in
>> > my
>> > debug folder, and one inside the AU.
>> > How does the code know where to find the bundle anyway? I mean, I
>> > understand
>> > that GetProperty is called with kAudioUnitProperty_CocoaUI, but in the
>> > template generated code there's no path or anything, there's just this
>> > code:
>> >
>> > CFBundleRef bundle = CFBundleGetBundleWithIdentifier(
>> > CFSTR("com.yourcompany.cocoatest") );
>> >
>> > if (bundle == NULL) return fnfErr;
>> >
>> >
>> >
>> > CFURLRef bundleURL = CFBundleCopyResourceURL( bundle,
>> >
>> > CFSTR("KeyToSoundcocoatest_CocoaViewFactory"),
>> >
>> > CFSTR("bundle"),
>> >
>> > NULL);
>> >
>> >
>> >
>> > So, I guess there's a search path, and the AU is (recursively) included
>> > in
>> > the search path? Or?
>> > Anyway, I'm not sure this is the cause of the my problem, just a wild
>> > guess.
>> >
>> > Thanks,
>> > Michael Olsen
>> >
>> >
>> > ________________________________
>> > Get news, entertainment and everything you care about at Live.com. Check
>> > it
>> > out!
>> > _______________________________________________
>> > 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
>> >
>>
>>
>>
>> --
>> www.marcelocnt.com
>> www.impa.br/~cicconet
>
> ____
_______________________________________________
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