Re: AU - CW code gen problems
Re: AU - CW code gen problems
- Subject: Re: AU - CW code gen problems
- From: Marc Poirier <email@hidden>
- Date: Fri, 28 Mar 2003 01:17:03 +0100 (CET)
Hi. I just ate a bowl of chili, so now I'm a little more calm. :)
I guess what I'm basically saying here is, given what I'm experiencing
with the example ultra-lean project that I put on the web, I can only
think of 3 possible explainations for my problems:
(1) CodeWarrior is producing bad code
(2) I've mis-configured my CW project
(3) There are serious bugs in the AUPublic SDK code that reveal
themselves when built by CW
I'm posting to the list about this because anyone else here building AUs
with CW will want to know what the final explaination is. Well, if it's
2, then maybe folks won't care so much, but 1 or 3 would affect us all.
Maybe I should posit a new question: Has anyone successfully built an AU
with a custom GUI using the Dec 2002 Dev Tools AU SDK and CodeWarrior 8.3?
If so, did you need to make any modifications to the AU SDK? If not,
would you care to send me your CW project or an example derived from it?
Thanks again,
Marc
On Fri, 28 Mar 2003, Marc Poirier wrote:
>
> This makes it sound like a good old fashioned memory stomper. At one
>
> point get crashes in random routines deep inside HIToolBox for running
>
> off the end of a HAL provided buffer.
>
>
I would be inclined to agree with you if it weren't for the sheer madness
>
of everything! Remember, like I said, I've tried building completely
>
skeletal code and it still crashes.
>
>
> Have you tried seeing if you get the crash if you provide just the DSP
>
> and no custom view?
>
>
No, actually. If I return 0 from GetNumCustomUIComponents, then I get no
>
crashes. But I still say that it's not my code.
>
>
Alright, if anyone is interested in witnessing such total madness, you can
>
download my ultra-stripped-down project here:
>
>
http://smartelectronix.com/~destroyfx/crash-machine.sit
>
>
Aside from the Apple SDK stuff, there is nothing! Well, except for my
>
implementations of GetNumCustomUIComponents and GetUIComponentDescs.
>
Other than that, it's just a couple of empty class constructors. Yet the
>
plugin crashes!
>
>
Also perhaps worth mentioning: I've tried this with a set of AUPublic
>
files from the Dec 2002 Dev Tools with only very minimal modifications,
>
only those posted by Philipe Wicker in this message (which are required to
>
get the files to build with CW):
>
http://lists.apple.com/archives/coreaudio-api/2003/Jan/30/audiounitcrashandfix.001.txt
>
and the MaintainKernels fix that I posted:
>
http://lists.apple.com/archives/coreaudio-api/2002/Dec/20/crashybugindecemberdevto.txt
>
>
Here are instructions for making it crash: In Logic, load the plugin.
>
Wait 3 seconds. In AudioUnitHosting, you may need to switch back and
>
forth between it and another plugin a few times before it crashes (you'll
>
need to use keyboard navigation for this because the window will disappear
>
when you load the plugin, since there's no UI code).
>
>
If anyone can explain this total madness, you get a prize!
>
>
Thanks again,
>
Marc
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.