Hello Dan,
On 11/09/2010 12:54 PM, Dan Loader wrote:
> 0CFRunLoopWakeUp00x98909721
> 1IODispatchCalloutFromCFMessage00x91b39000
> 2IODispatchCalloutFromMessage00x91b390cd
> 3__CFMachPortPerform00x988e73a2
> 4__CFRunLoopRun00x988e310b
> 5CFRunLoopRunSpecific00x988e1094
> 6CFRunLoopRunInMode00x988e0ec1
> *==> 7usb_bulk_transferdarwin.c8410x0166a0fc*
> 8usb_bulk_readdarwin.c9130x0166a4e1
> 9ftdi_read_dataftdi.c15670x0002f671
> 10SerialListener::_readFromDeviceSerialListener.cpp650x0000c332
> 11SerialListener::runSerialListener.cpp310x000093de
> 12QThreadPrivate::start00x00c6e35b
> 13_pthread_start00x968b27fd
> 14thread_start00x968b2682
>
> Line 841 of darwin.c is:
>
> *if (CFRunLoopRunInMode(kCFRunLoopDefaultMode, (timeout+999)/1000, true) ==
> kCFRunLoopRunTimedOut) {*
Is "valgrind" available on Mac OS X?
That's the first thing I do if a program crashes
and it's not really obvious why.
Does the mentioned code access libftdi
from multiple threads at the same time?
Cheers,
Thomas
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
