Re: A freezing bug
Re: A freezing bug
- Subject: Re: A freezing bug
- From: Jeff Moore <email@hidden>
- Date: Thu, 8 Jan 2004 11:45:40 -0800
Hmm. Can you ssh into the machine and do anything useful? If you can,
attaching with gdb would be the most useful thing to do. In fact, being
attached prior to the hang happening would be best.
Otherwise, you're stuck with logging. The sort of info I'd include in
every log are things like the host time, the thread id, and something
that leads me back to where in the source the log came from. I wouldn't
worry about glitching or other side effects of issuing printf or syslog
calls from the IO thread unless they perturb the behavior of the bug.
In that case, I'd log to a pre-allocated block of memory and write it
to a file after the fact.
It sounds to me like something is spinning in the IO thread, so you'll
probably be logging to see the chain of events in the IO thread that
leads up to the hang. The time stamps should reveal the before and
after nicely.
On Jan 8, 2004, at 5:15 AM, Robert Grant wrote:
I've got a bug in my app where it will freeze the entire system
(except the mouse still moves). It seems to be the DefaultOutputUnit
that's getting confused, but I'm not sure what I could have done that
would cause it to block the HAL IOProc (which is what I think causes
this problem). It seems to happen when I'm messing about attaching and
detaching AudioUnits to the DefaultOutputUnit.
Thanks for any sleuthing tips,
Robert.
_______________________________________________
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.
--
Jeff Moore
Core Audio
Apple
_______________________________________________
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.