• 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: Crashing Auval
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Crashing Auval


  • Subject: RE: Crashing Auval
  • From: "Michael Ljunggren" <email@hidden>
  • Date: Thu, 20 Apr 2006 12:29:01 +0200
  • Organization: Alien Connections

Hi Bill, and thanks!

The problem is solved now. It was not due to auval, but oddly
enough not my program either...! It was Xcode (2.2.1). sigh...

I was unable to debug of the same reason the program crashed,
namely, Xcode had not properly re-linked the code for 4 hours!
I was running with an old binary and setting breakpoints in new source
code, thus never hitting them on the spot.

I would report this bug if I didn't knew Xcode 2.3 is coming shortly.

Thanks again, the code was pretty good already, and now it is validated by
auval :-)
/Michael


> > (I inherit AUEffectBase and call it awxAuWrapper.) The first that
> > happens
> > during validation is that my main object, awxAuWrapper, is created
> > and tests run on it,
> > but what I don't understand why my object is deleted during mid-
> > tests? Auval
> > is calling CloseComponent but continue to run the tests. Is this a
> > part of the test
> > or have I fooled auval into doing something bad?
>
> auval is opening two instances of your AU - it then closes one of
> these, and proceeds to the rest of its work with the other. You will
> get two objects of your AUEffectBase being created as a result of
> this, one disposed of, the other used.
>
> >
> > A precursor to the crash is when I get a bunch of "AssertMacros"
> > from AUBase in my log
> > (I will post them if anyone cares to read them.)
>
> You'll get alot of these - part of the tests auval runs is to make
> sure the basic property semantics are correct (which includes
> getting
> errors back for unimplemented properties). This is all normal - I
> actually pipe stderr to null so I don't see these:
>
> auval 2> /dev/null -v aufx bpas appl
>
>
> You should probably run this with the debugger so you can see
> exactly
> where you are crashing in auval. Nothing you've described so far is
> unexpected.
>
> Bill
>
> >
> > Regards, Michael Ljunggren
> > Alien Connections
> >
> >  _______________________________________________
> > 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
>
> --
> mailto:email@hidden
> tel: +1 408 974 4056
> ______________________________________________________________
> __________
> __
> "Much human ingenuity has gone into finding the ultimate Before.
> The current state of knowledge can be summarized thus:
> In the beginning, there was nothing, which exploded" - Terry Pratchett
> ______________________________________________________________
> __________
> __

 _______________________________________________
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

References: 
 >Re: Crashing Auval (From: William Stewart <email@hidden>)

  • Prev by Date: Re: OT: xcode and cvs
  • Next by Date: Re: siCompressionParams Question
  • Previous by thread: Re: Crashing Auval
  • Next by thread: ExtAudioFileSeek and Tell
  • Index(es):
    • Date
    • Thread