Re: diagnostic logging for use in audio threads?
Re: diagnostic logging for use in audio threads?
- Subject: Re: diagnostic logging for use in audio threads?
- From: Herbie Robinson <email@hidden>
- Date: Sun, 13 Apr 2003 16:12:08 -0400
Another technique is to put a lot of sanity checks in the code and
increment counters when they go off. Also, statistic counters can at
times be helpful. No matter what you do, the debugging code will
impact performance to some extent.
At 12:27 AM -0700 4/13/03, Jeff Moore wrote:
When I'm doing performance sensitive logging, I will write all the
data to a ring buffer from the IO thread and use another low
priority work thread to flush the ring buffer to a file on the disk.
Works like a charm.
On Saturday, April 12, 2003, at 07:07 PM, Kurt Bigler wrote:
Are there any C/C++ compatible text logging functions out there
that are appropriate for use in an IOProc thread?
Searching the archives only led me to NSLog (or something like
that) which is an ObjC solution.
Of course, a memory-only logging solution would probably be ideal,
but I am not expecting that anything like that exists (but would
love to be proven wrong). An ideal solution I think would log to
memory in a multi-thread-safe way, with the help of a utility app
that could be used to read the log.
Are people using file-based logging in their io threads? If so do
the logging calls tend to badly cripple the performance of things,
interfering with the process that is being diagnosed?
--
-*****************************************
**
http://www.curbside-recording.com/ **
******************************************
_______________________________________________
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.