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

Re: AudioConverter IOProcs


  • Subject: Re: AudioConverter IOProcs
  • From: kante easley <email@hidden>
  • Date: Sun, 4 Apr 2004 13:35:17 -0400

On Sunday, April 4, 2004, at 04:04 AM, Philippe Wicker wrote:

On Apr 4, 2004, at 8:46 AM, kante easley wrote:

I hope this is an appropriate question for the list:

It is :)


Using project builder, my program runs through with no problems in debug mode. When build and run (not debugging) I get a memory error (signal 11 (SIGSEGV)).

Do you mean that you compiled your code without -g flag? If yes, try to compile it with this flag set (it adds debug info wether the generated machine code is optimized or not) and launch your program under gdb, it should show you where the SIGSEGV occurs. If your program is not launched under gdb, you may also have a look to the log trace, it tells you in which thread and which function call this signal occured.

If you mean that the same code compiled with the same C flags works well under debugger, and crashes when it runs by itself, then this may be a pointer badly initialized which "luckily" points within your app address space in the first case (under gdb), and outside in the second case (running by itself). Using the log trace could give a help.

I meant that the code compiles, and runs fine when I put it through the ProjectBuilder debugger (I'm still a bit GUI-dependent). I was looking for pointer errors as you suggested but could find none. Thanks for the log trace tip though, I'll certainly figure out how to use it before I ask next time!

It turns out that I had forgotten to fflush( stdout ) after one of my user messages. I was receiving 200+ OSStatus errors telling me that one of my parameters was wrong, all of which were being jammed into stdout when the program ran on it's own. I was so focused on pointers that I didn't even notice!


I believe that the error has something to do with my input IOProc used in multiple calls to AudioConverterFillComplexBuffer.

What do you mean by "multiple calls to AudioConverterFillComplexBuffer"?

I just meant that I had filled an AudioBufferList[] with input and was iterating through the array to do the conversion.

I'm still curious as to what circumstances require one to Add_Load_To_IOProc, as implied in Daisy's code. The mailing list archive search hasn't worked for me in the last few days ( or right now ) so I apologize if this has been asked millions of times before.

Thanks again,

Kante Easley
_______________________________________________
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.


References: 
 >Re: AudioConverter IOProcs (From: Philippe Wicker <email@hidden>)

  • Prev by Date: Re: Variable IO in AU?
  • Next by Date: Re: CoreAudio Swiki site problem
  • Previous by thread: Re: AudioConverter IOProcs
  • Next by thread: Variable IO in AU?
  • Index(es):
    • Date
    • Thread