Re: DeviceIsDead
Re: DeviceIsDead
- Subject: Re: DeviceIsDead
- From: Jeff Moore <email@hidden>
- Date: Fri, 29 Apr 2005 13:57:27 -0700
That back trace indicates that the HAL is crashing when it is
receiving the notification from IOKit that the device has gone away.
Generally speaking, this sort of crash is an indication of some
memory corruption somewhere, but it's hard to say for sure.
Do you have any more context you can provide? What's going on in the
other threads? Have you tried running your app with GuardMalloc or
MallocDebug?
On Apr 29, 2005, at 1:23 PM, Lubor Prikryl wrote:
Hello,
I am solving an issue when my app is crashing after unplugging FW
and USB devices.
What I do obtaining a notification:
Remove all listening to device and stream notifications for this
device
Stop the device
Remove callback
After that, the application crashes as it seems that the CA thread
attempts to continue with the device
#0 0x907455dc in IOAPlugIn::DeviceIsDead(IOADevice*)
#1 0x9075aa04 in IOADevice::IOServiceInterestCallback(void*,
unsigned, unsigned, void*)
#2 0x905a2570 in IODispatchCalloutFromCFMessage
#3 0x901dd280 in __CFMachPortPerform
#4 0x901d9a04 in __CFRunLoopDoSource1
#5 0x901c18d0 in __CFRunLoopRun
#6 0x901c5e6c in CFRunLoopRunSpecific
#7 0x90732f80 in HALRunLoop::OwnThread(void*)
#8 0x907391e0 in CAPThread::Entry(CAPThread*)
#9 0x90024910 in _pthread_body
What else should I do after the device is disconnected to avoid it?
--
Jeff Moore
Core Audio
Apple
_______________________________________________
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: | |
| | >DeviceIsDead (From: Lubor Prikryl <email@hidden>) |